CVS corruption/mistagging?
in [PgSql]
|
Prev: Bug: Buffer cache is not scan resistant
Next: CREATE DATABASE cannot be executed from a function or multi-command string
From: Tom Lane on 15 Aug 2007 00:13 "Marc G. Fournier" <scrappy(a)hub.org> writes: > It should be done ... if you try and create a tag, it should generate > an error message ... Uh, nope: $ cvs tag fooey README T README $ cvs log README | more RCS file: /cvsroot/pgsql/src/backend/optimizer/README,v Working file: README head: 1.39 branch: locks: strict access list: symbolic names: fooey: 1.39 REL7_3_19: 1.25 REL7_4_17: 1.29 REL8_0_13: 1.30 REL8_1_9: 1.33 REL8_2_4: 1.35.2.1 REL8_0_12: 1.30 REL8_1_8: 1.33 REL8_2_3: 1.35 REL7_3_18: 1.25 REL7_4_16: 1.29 REL8_0_11: 1.30 REL8_1_7: 1.33 REL8_2_2: 1.35 REL8_0_10: 1.30 cvs [log aborted]: received broken pipe signal $ cvs tag -d fooey README D README $ regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
From: "Marc G. Fournier" on 15 Aug 2007 00:22 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 'k, let me play with it ... - --On Wednesday, August 15, 2007 00:13:11 -0400 Tom Lane <tgl(a)sss.pgh.pa.us> wrote: > "Marc G. Fournier" <scrappy(a)hub.org> writes: >> It should be done ... if you try and create a tag, it should generate >> an error message ... > > Uh, nope: > > $ cvs tag fooey README > T README > $ cvs log README | more > > RCS file: /cvsroot/pgsql/src/backend/optimizer/README,v > Working file: README > head: 1.39 > branch: > locks: strict > access list: > symbolic names: > fooey: 1.39 > REL7_3_19: 1.25 > REL7_4_17: 1.29 > REL8_0_13: 1.30 > REL8_1_9: 1.33 > REL8_2_4: 1.35.2.1 > REL8_0_12: 1.30 > REL8_1_8: 1.33 > REL8_2_3: 1.35 > REL7_3_18: 1.25 > REL7_4_16: 1.29 > REL8_0_11: 1.30 > REL8_1_7: 1.33 > REL8_2_2: 1.35 > REL8_0_10: 1.30 > cvs [log aborted]: received broken pipe signal > $ cvs tag -d fooey README > D README > $ > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 7: You can help support the PostgreSQL project by donating at > > http://www.postgresql.org/about/donate - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy(a)hub.org MSN . scrappy(a)hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFGwn9q4QvfyHIvDvMRAuqOAJwPcIcsfQ74wBwdjBR478C72nr+bwCfd8PY EeH2sh+biTfoFbTF2KxqYVU= =iMwZ -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
From: "Marc G. Fournier" on 15 Aug 2007 01:06 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 One better (and done now): find . -nouser -exec chown scrappy {} \; so, all files that had valid users owning them stay with those ... - --On Wednesday, August 15, 2007 00:08:07 -0400 Tom Lane <tgl(a)sss.pgh.pa.us> wrote: > "Marc G. Fournier" <scrappy(a)hub.org> writes: >>> That was a good thing, but for security's sake these files ought to be >>> chown'd to some existing committer's account. > >> I can do a quick chown -R scrappy on the whole repository ... ok? > > Seems close enough, but please keep that tarball around for awhile just > in case we need to look at the prior state. > > regards, tom lane - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy(a)hub.org MSN . scrappy(a)hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFGwonj4QvfyHIvDvMRAhNBAJ9b6Y1o4eICLrtuWncRIqN8g07XggCgnnc8 ttJoOScGbFEY/y3qP3MZYWY= =RUO5 -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
From: Tom Lane on 15 Aug 2007 01:17 "Marc G. Fournier" <scrappy(a)hub.org> writes: > One better (and done now): > find . -nouser -exec chown scrappy {} \; [ eyeballs repository ... ] Check, that looks great from here. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo(a)postgresql.org so that your message can get through to the mailing list cleanly
From: Magnus Hagander on 15 Aug 2007 01:55
Tom Lane wrote: > In the meantime, though, it's not quite clear why this would lead to > a buildfarm failure --- it should just mean a lot of extraneous files > appearing in a fresh checkout. (Looks a bit harder ... Oh, it looks > like btree_gist has some files that used to be autogenerated and are > now in CVS, so the bogusly new versions from CVS are suppressing the > desired generation from the old btree_num.c file.) Funny enoughy, that's exactly the problem I saw on win32 when I rsynced from a windows box and tried a local CVS checkout :-) Once I rsynced to a local linux instead and checked out from there, things worked again :) //Magnus ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |