[COMMITTERS] pgsql: Ensure that the resolved datatype of any unknown Param is

2005-02-19 Thread Tom Lane
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/backe

[COMMITTERS] pgsql: Ensure that the resolved datatype of any unknown Param is

2005-02-19 Thread Tom Lane
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/backe

[COMMITTERS] pgsql: Ensure that the resolved datatype of any unknown Param is

2005-02-19 Thread Tom Lane
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

[COMMITTERS] pgsql: New arrangement to always let the bgwriter do checkpoints broke

2005-02-19 Thread Tom Lane
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/

[COMMITTERS] pgsql: New arrangement to always let the bgwriter do checkpoints broke

2005-02-19 Thread Tom Lane
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: bgwrit

[COMMITTERS] pgsql: Add code to prevent transaction ID wraparound by enforcing a safe

2005-02-19 Thread Tom Lane
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 datfro

[COMMITTERS] pgpool - pgpool: make some logs from log level to debug level

2005-02-19 Thread User T-ishii
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) ---

[COMMITTERS] pgpool - pgpool: version 2.5.1

2005-02-19 Thread User T-ishii
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/pgp

[COMMITTERS] pgpool - pgpool: Emit log when pgpool starts up

2005-02-19 Thread User T-ishii
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)

[COMMITTERS] pgsql: Flat file cleanup phase 2: make it work for pg_group.

2005-02-19 Thread Tom Lane
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

[COMMITTERS] pgsql: I have added a define, MAKE_ALL_TUPLES_VISIBLE, to help people

2005-02-19 Thread Bruce Momjian
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.postgr