[COMMITTERS] pgbouncer - pgbouncer: correct check in incomplete_pkt()
Log Message: --- correct check in incomplete_pkt() Modified Files: -- pgbouncer/src: proto.h (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/src/proto.h.diff?r1=1.2&r2=1.3) ---(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
[COMMITTERS] pgbouncer - pgbouncer: make fatal_perror() really fatal
Log Message: --- make fatal_perror() really fatal Modified Files: -- pgbouncer/src: util.c (r1.12 -> r1.13) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/src/util.c.diff?r1=1.12&r2=1.13) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgbouncer - pgbouncer: fix comments
Log Message: --- fix comments Modified Files: -- pgbouncer/src: proto.c (r1.9 -> r1.10) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/src/proto.c.diff?r1=1.9&r2=1.10) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgbouncer - pgbouncer: no need to use disconnect_client() as
Log Message: --- no need to use disconnect_client() as disconnect_server also notifies client Modified Files: -- pgbouncer/src: server.c (r1.13 -> r1.14) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/src/server.c.diff?r1=1.13&r2=1.14) ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be
Tom Lane wrote: There seems to be something wrong with this commit notification. This file > pgsql/src/test/regress/expected: > foreign_key.out (r1.44 -> r1.45) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/foreign_key.out?r1=1.44&r2=1.45) does not seem to have a 1.45 revision. Indeed, the changeset in this patch for this file is in 1.44, not 1.45. Any ideas what might have happened? Maybe this was changed when the bogus REL7_4_STABLE tag was removed? -- Alvaro Herrera http://www.PlanetPostgreSQL.org/ "I think my standards have lowered enough that now I think 'good design' is when the page doesn't irritate the living f*ck out of me." (JWZ) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
cvsweb busted (was Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be)
Alvaro Herrera <[EMAIL PROTECTED]> writes: > There seems to be something wrong with this commit notification. This > file >> pgsql/src/test/regress/expected: >> foreign_key.out (r1.44 -> r1.45) >> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/foreign_key.out?r1=1.44&r2=1.45) > does not seem to have a 1.45 revision. Indeed, the changeset in this > patch for this file is in 1.44, not 1.45. No, 1.44 was a month ago. 1.45 does exist in the master CVS repo AFAICS. It looks to me like cvsweb is showing a version that hasn't gotten updated for a day or two. Some fallout of the master server move no doubt. regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: cvsweb busted (was Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be)
Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: >> There seems to be something wrong with this commit notification. This >> file > >>> pgsql/src/test/regress/expected: >>> foreign_key.out (r1.44 -> r1.45) >>> (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/foreign_key.out?r1=1.44&r2=1.45) > >> does not seem to have a 1.45 revision. Indeed, the changeset in this >> patch for this file is in 1.44, not 1.45. > > No, 1.44 was a month ago. 1.45 does exist in the master CVS repo > AFAICS. > > It looks to me like cvsweb is showing a version that hasn't gotten > updated for a day or two. Some fallout of the master server move > no doubt. Yes, it seems to be caused by the bug in the rsync server on the old machine. It gets fixed eventually by itself (I pushed it through now). Marc - how much work to update that one on the old server? I know you have a new one coming up, but as a stop-gap fix on the old one? //Magnus ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Add: > > * Reduce XID consumption of read-only queries > >
Log Message: --- Add: > > * Reduce XID consumption of read-only queries > >http://archives.postgresql.org/pgsql-hackers/2007-08/msg00516.php > Modified Files: -- pgsql/doc/src/FAQ: TODO.html (r1.712 -> r1.713) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html?r1=1.712&r2=1.713) ---(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
[COMMITTERS] pgbouncer - pgbouncer: server->setting_vars should be checked in
Log Message: --- server->setting_vars should be checked in SBUF_EV_FLUSH instead Modified Files: -- pgbouncer/src: server.c (r1.14 -> r1.15) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/src/server.c.diff?r1=1.14&r2=1.15) ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] Re: cvsweb busted (was Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Thursday, August 16, 2007 18:29:22 +0200 Magnus Hagander <[EMAIL PROTECTED]> wrote: > Marc - how much work to update that one on the old server? I know you > have a new one coming up, but as a stop-gap fix on the old one? The new one is just waiting on your time scheduale ... its there ready for you though :) - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFGxLb74QvfyHIvDvMRAp7KAKDna1ykPMPMKA7swknKg8aHnJ0d7QCg5T5A yJKd0uDb7FBvm2EeZtS3ioA= =DxVn -END PGP SIGNATURE- ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [HACKERS] Re: cvsweb busted (was Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be)
Marc G. Fournier wrote: > >> Marc - how much work to update that one on the old server? I know you >> have a new one coming up, but as a stop-gap fix on the old one? > > The new one is just waiting on your time scheduale ... its there ready for > you > though :) No, that's still waiting on your documentation. But my question still stands - how much work to stop-gap fix it on the old one? //Magnus ---(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
[COMMITTERS] edb-debugger - server: Auto-creating stats table if needed, creating
Log Message: --- Auto-creating stats table if needed, creating custom GUC variables at plugin load instead of waiting until the profiler is first used Modified Files: -- server: plugin_profiler.c (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/edb-debugger/server/plugin_profiler.c.diff?r1=1.2&r2=1.3) ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] Re: cvsweb busted (was Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Thursday, August 16, 2007 23:16:09 +0200 Magnus Hagander <[EMAIL PROTECTED]> wrote: > > But my question still stands - how much work to stop-gap fix it on the > old one? rsync should be upgraded now ... - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFGxOT94QvfyHIvDvMRAvzDAJ99kLdDzyM9RsxeUi1aQOyoJLv+sQCgkq/e tRC1QXW116gVX/30VZCJQGc= =e7HB -END PGP SIGNATURE- ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Re: cvsweb busted (was Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be)
Marc G. Fournier wrote: > > > --On Thursday, August 16, 2007 23:16:09 +0200 Magnus Hagander > <[EMAIL PROTECTED]> wrote: > >> But my question still stands - how much work to stop-gap fix it on the >> old one? > > rsync should be upgraded now ... Thanks! Hopefully that should fix the short-term problem. I'll try to take a look at the other one as soon as I can, hopefully this weekend - if you have the docs by then. //Magnus ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
