[COMMITTERS] pgsql: Revert (again) GUC patch to return commented fields to their

Log Message: --- Revert (again) GUC patch to return commented fields to their default values, due to concern about the patch. Modified Files: -- pgsql/src/backend/utils/misc: guc-file.l (r1.44 -> r1.45) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/

[COMMITTERS] pgsql: Get rid of "lookahead" functionality in plpgsql's yylex()

Log Message: --- Get rid of "lookahead" functionality in plpgsql's yylex() function, and instead make the grammar production for the RETURN statement do the heavy lifting. The lookahead idea was copied from the main parser, but it does not work in plpgsql's parser because here gram.y looks

[COMMITTERS] pgsql: Get rid of "lookahead" functionality in plpgsql's yylex()

Log Message: --- Get rid of "lookahead" functionality in plpgsql's yylex() function, and instead make the grammar production for the RETURN statement do the heavy lifting. The lookahead idea was copied from the main parser, but it does not work in plpgsql's parser because here gram.y looks

[COMMITTERS] npgsql - Npgsql: 2006-08-13 Josh Cooley <[EMAIL PROTECTED]>

Log Message: --- 2006-08-13 Josh Cooley <[EMAIL PROTECTED]> * Fixed command builders GetInsertCommand, GetUpdateCommand, and GetDeleteCommand to use the values from the row passed when called directly. Modified Files: -- Npgsql/src/Npgsql: NpgsqlCommandBuild

[COMMITTERS] pgsql: Fix core dump in duration logging for a V3-protocol Execute

Log Message: --- Fix core dump in duration logging for a V3-protocol Execute message when what's being executed is a COMMIT or ROLLBACK. Per report from Sergey Koposov. Backpatch to 8.1; 8.0 and before don't have the bug due to lack of any logging at all here. Tags: REL8_1_STABLE M

[COMMITTERS] pgsql: Fix core dump in duration logging for a V3-protocol Execute

Log Message: --- Fix core dump in duration logging for a V3-protocol Execute message when what's being executed is a COMMIT or ROLLBACK. Per report from Sergey Koposov. Backpatch to 8.1; 8.0 and before don't have the bug due to lack of any logging at all here. Modified Files: ---

[COMMITTERS] pgsql: Cause psql to report both the returned data and the command

Log Message: --- Cause psql to report both the returned data and the command status tag for INSERT/UPDATE/DELETE RETURNING. Per discussion. Modified Files: -- pgsql/src/bin/psql: common.c (r1.123 -> r1.124) (http://developer.postgresql.org/cvsweb.cgi/pgsql

[COMMITTERS] python - fe: Add a --pq-trace option for logging protocol communication.

Log Message: --- Add a --pq-trace option for logging protocol communication. Modified Files: -- fe/src: python.py (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/python.py.diff?r1=1.2&r2=1.3) ---(end of bro

[COMMITTERS] python - ip: Provide a means for passing args and kw to connection

Log Message: --- Provide a means for passing args and kw to connection instantiation. Modified Files: -- ip/src: python.py (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/ip/src/python.py.diff?r1=1.4&r2=1.5) ---(e

[COMMITTERS] pgsql: If test postmaster fails to start within 60 seconds, try to kill

Log Message: --- If test postmaster fails to start within 60 seconds, try to kill -9 it so that it won't interfere with later trials. Per recent buildfarm experience. Anyone know how to do this on Windows? Modified Files: -- pgsql/src/test/regress: pg_regress.c (r

[COMMITTERS] pgsql: Extend 'guc' regression test to check manipulations of datestyle

Log Message: --- Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects

[COMMITTERS] pgsql: Original coding of 'returning' regression test inadvertently

Log Message: --- Original coding of 'returning' regression test inadvertently chose a nonunique join value, leading to plan-choice-dependent results ... and it seems some platforms will choose a different plan. Tweak the test so that it has well-defined results. Per report from Olivier Pr

[COMMITTERS] pgsql: Back out plperl OUT hash/array parameter patch, again.

Log Message: --- Back out plperl OUT hash/array parameter patch, again. Modified Files: -- pgsql/src/pl/plperl: plperl.c (r1.116 -> r1.117) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.c.diff?r1=1.116&r2=1.117) pgsql/src/pl/plp

[COMMITTERS] xlogviewer - xlogdump:

Log Message: --- Modified Files: -- xlogdump: .kdbgrc.xlogdump (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/xlogviewer/xlogdump/.kdbgrc.xlogdump.diff?r1=1.5&r2=1.6) xlogdump (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/c

[COMMITTERS] pgsql: Fix recent guc comment-to-default patch for custom variables.

Log Message: --- Fix recent guc comment-to-default patch for custom variables. Modified Files: -- pgsql/src/backend/utils/misc: guc.c (r1.339 -> r1.340) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.339&r2=1.340)

[COMMITTERS] xlogviewer - xlogdump:

Log Message: --- Modified Files: -- xlogdump/test/expected: dump.result (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/xlogviewer/xlogdump/test/expected/dump.result.diff?r1=1.2&r2=1.3) names.result (r1.2 -> r1.3) (http://cvs.p

[COMMITTERS] xlogviewer - xlogdump:

Log Message: --- Modified Files: -- xlogdump: .kdbgrc.xlogdump (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/xlogviewer/xlogdump/.kdbgrc.xlogdump.diff?r1=1.4&r2=1.5) xlogdump (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/c

[COMMITTERS] pgsql: Applied patch for VPATH builds by Alvaro Herrera

Log Message: --- Applied patch for VPATH builds by Alvaro Herrera <[EMAIL PROTECTED]> Merged dyntest.pgc and dyntest2.pgc. Hopefully fixed the last Coverity reports (finally) Modified Files: -- pgsql/src/interfaces/ecpg/ecpglib: connect.c (r1.32 -> r1.33) (