[COMMITTERS] pgsql: Ensure that the resolved datatype of any unknown Param is
Log Message: --- Ensure that the resolved datatype of any unknown Param is propagated into the sub-SELECT targetlist when it appears in the context INSERT INTO foo SELECT $1 ... Per report from Abhijit Menon-Sen. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/parser: analyze.c (r1.314 -> r1.314.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c.diff?r1=1.314&r2=1.314.4.1) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Ensure that the resolved datatype of any unknown Param is
Log Message: --- Ensure that the resolved datatype of any unknown Param is propagated into the sub-SELECT targetlist when it appears in the context INSERT INTO foo SELECT $1 ... Per report from Abhijit Menon-Sen. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/backend/parser: analyze.c (r1.290.2.2 -> r1.290.2.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c.diff?r1=1.290.2.2&r2=1.290.2.3) ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Ensure that the resolved datatype of any unknown Param is
Log Message: --- Ensure that the resolved datatype of any unknown Param is propagated into the sub-SELECT targetlist when it appears in the context INSERT INTO foo SELECT $1 ... Per report from Abhijit Menon-Sen. Modified Files: -- pgsql/src/backend/parser: analyze.c (r1.314 -> r1.315) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c.diff?r1=1.314&r2=1.315) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: New arrangement to always let the bgwriter do checkpoints broke
Log Message: --- New arrangement to always let the bgwriter do checkpoints broke CHECKPOINT and some other commands in the context of a standalone backend. Allow a standalone backend to do its own checkpoints. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/postmaster: bgwriter.c (r1.13 -> r1.13.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/bgwriter.c.diff?r1=1.13&r2=1.13.4.1) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[COMMITTERS] pgsql: New arrangement to always let the bgwriter do checkpoints broke
Log Message: --- New arrangement to always let the bgwriter do checkpoints broke CHECKPOINT and some other commands in the context of a standalone backend. Allow a standalone backend to do its own checkpoints. Modified Files: -- pgsql/src/backend/postmaster: bgwriter.c (r1.13 -> r1.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/bgwriter.c.diff?r1=1.13&r2=1.14) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[COMMITTERS] pgsql: Add code to prevent transaction ID wraparound by enforcing a safe
Log Message: --- Add code to prevent transaction ID wraparound by enforcing a safe limit in GetNewTransactionId(). Since the limit value has to be computed before we run any real transactions, this requires adding code to database startup to scan pg_database and determine the oldest datfrozenxid. This can conveniently be combined with the first stage of an attack on the problem that the 'flat file' copies of pg_shadow and pg_group are not properly updated during WAL recovery. The code I've added to startup resides in a new file src/backend/utils/init/flatfiles.c, and it is responsible for rewriting the flat files as well as initializing the XID wraparound limit value. This will eventually allow us to get rid of GetRawDatabaseInfo too, but we'll need an initdb so we can add a trigger to pg_database. Modified Files: -- pgsql/doc/src/sgml: maintenance.sgml (r1.40 -> r1.41) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/maintenance.sgml.diff?r1=1.40&r2=1.41) pgsql/src/backend/access/transam: varsup.c (r1.60 -> r1.61) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/varsup.c.diff?r1=1.60&r2=1.61) xact.c (r1.195 -> r1.196) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xact.c.diff?r1=1.195&r2=1.196) pgsql/src/backend/bootstrap: bootstrap.c (r1.198 -> r1.199) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/bootstrap/bootstrap.c.diff?r1=1.198&r2=1.199) pgsql/src/backend/commands: dbcommands.c (r1.149 -> r1.150) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c.diff?r1=1.149&r2=1.150) user.c (r1.148 -> r1.149) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/user.c.diff?r1=1.148&r2=1.149) vacuum.c (r1.300 -> r1.301) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.300&r2=1.301) pgsql/src/backend/libpq: hba.c (r1.137 -> r1.138) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/hba.c.diff?r1=1.137&r2=1.138) pgsql/src/backend/postmaster: postmaster.c (r1.443 -> r1.444) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.443&r2=1.444) pgsql/src/backend/tcop: postgres.c (r1.440 -> r1.441) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c.diff?r1=1.440&r2=1.441) pgsql/src/backend/utils/init: Makefile (r1.17 -> r1.18) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/Makefile.diff?r1=1.17&r2=1.18) pgsql/src/include/access: transam.h (r1.51 -> r1.52) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/transam.h.diff?r1=1.51&r2=1.52) pgsql/src/include/commands: user.h (r1.25 -> r1.26) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/commands/user.h.diff?r1=1.25&r2=1.26) Added Files: --- pgsql/src/backend/utils/init: flatfiles.c (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/flatfiles.c?rev=1.1&content-type=text/x-cvsweb-markup) pgsql/src/include/utils: flatfiles.h (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/flatfiles.h?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgpool - pgpool: make some logs from log level to debug level
Log Message: --- make some logs from log level to debug level Modified Files: -- pgpool: pool_process_query.c (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgpool/pgpool/pool_process_query.c.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TIP 3: 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
[COMMITTERS] pgpool - pgpool: version 2.5.1
Log Message: --- version 2.5.1 Modified Files: -- pgpool: ChangeLog (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgpool/pgpool/ChangeLog.diff?r1=1.2&r2=1.3) NEWS (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgpool/pgpool/NEWS.diff?r1=1.2&r2=1.3) TODO (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgpool/pgpool/TODO.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgpool - pgpool: Emit log when pgpool starts up
Log Message: --- Emit log when pgpool starts up Modified Files: -- pgpool: main.c (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgpool/pgpool/main.c.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Flat file cleanup phase 2: make it work for pg_group.
Log Message: --- Flat file cleanup phase 2: make it work for pg_group. The flat group file now identifies group members by usesysid not name; this avoids needing to depend on SearchSysCache which we can't use during startup. (The old representation was entirely broken anyway, since we did not regenerate the file following RENAME USER.) It's only a 95% solution because if the group membership list is big enough to be toasted out of line, we cannot read it during startup. I think this will do for the moment, until we have time to implement the planned pg_role replacement for pg_group. Modified Files: -- pgsql/src/backend/libpq: crypt.c (r1.61 -> r1.62) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/crypt.c.diff?r1=1.61&r2=1.62) hba.c (r1.138 -> r1.139) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/hba.c.diff?r1=1.138&r2=1.139) pgsql/src/backend/utils/init: flatfiles.c (r1.1 -> r1.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/flatfiles.c.diff?r1=1.1&r2=1.2) ---(end of broadcast)--- TIP 3: 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
[COMMITTERS] pgsql: I have added a define, MAKE_ALL_TUPLES_VISIBLE, to help people
Log Message: --- I have added a define, MAKE_ALL_TUPLES_VISIBLE, to help people recover deleted tuples. Of course it is only to be used for disaster recovery. Modified Files: -- pgsql/src/backend/utils/time: tqual.c (r1.81 -> r1.82) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/tqual.c.diff?r1=1.81&r2=1.82) ---(end of broadcast)--- TIP 8: explain analyze is your friend
