[COMMITTERS] pllolcode - pllolcode: Fix memory errors, and make parser return parse

2009-05-01 Thread User Eggyknap
Log Message: --- Fix memory errors, and make parser return parse tree. Also add new tests and some initial infrastructure for long-term parse tree storage Modified Files: -- pllolcode: DOC (r1.28 -> r1.29) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolc

[COMMITTERS] pgsql: Fix a couple of cases where the plpgsql grammar looked for T_WORD

2009-05-01 Thread Tom Lane
Log Message: --- Fix a couple of cases where the plpgsql grammar looked for T_WORD and failed to consider the possibility that it would get T_SCALAR, T_RECORD, or T_ROW instead because the word happens to match a plpgsql variable name. In particular, give "duplicate declaration" rather than

[COMMITTERS] pg-migrator - src: Minor cleanups.

2009-05-01 Thread User Bmomjian
Log Message: --- Minor cleanups. Modified Files: -- src: TODO (r1.30 -> r1.31) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pg-migrator/src/TODO.diff?r1=1.30&r2=1.31) info.c (r1.9 -> r1.10) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pg-mi

[COMMITTERS] pgsql: When checking for datetime field overflow, we should allow a

2009-05-01 Thread Tom Lane
Log Message: --- When checking for datetime field overflow, we should allow a fractional-second part that rounds up to exactly 1.0 second. The previous coding rejected input like "00:12:57.", with the exact number of nines needed to cause failure varying dependi

[COMMITTERS] pgsql: When checking for datetime field overflow, we should allow a

2009-05-01 Thread Tom Lane
Log Message: --- When checking for datetime field overflow, we should allow a fractional-second part that rounds up to exactly 1.0 second. The previous coding rejected input like "00:12:57.", with the exact number of nines needed to cause failure varying dependi

[COMMITTERS] pgsql: When checking for datetime field overflow, we should allow a

2009-05-01 Thread Tom Lane
Log Message: --- When checking for datetime field overflow, we should allow a fractional-second part that rounds up to exactly 1.0 second. The previous coding rejected input like "00:12:57.", with the exact number of nines needed to cause failure varying dependi

[COMMITTERS] pgsql: When checking for datetime field overflow, we should allow a

2009-05-01 Thread Tom Lane
Log Message: --- When checking for datetime field overflow, we should allow a fractional-second part that rounds up to exactly 1.0 second. The previous coding rejected input like "00:12:57.", with the exact number of nines needed to cause failure varying dependi

[COMMITTERS] pgsql: When checking for datetime field overflow, we should allow a

2009-05-01 Thread Tom Lane
Log Message: --- When checking for datetime field overflow, we should allow a fractional-second part that rounds up to exactly 1.0 second. The previous coding rejected input like "00:12:57.", with the exact number of nines needed to cause failure varying dependi

[COMMITTERS] pgsql: When checking for datetime field overflow, we should allow a

2009-05-01 Thread Tom Lane
Log Message: --- When checking for datetime field overflow, we should allow a fractional-second part that rounds up to exactly 1.0 second. The previous coding rejected input like "00:12:57.", with the exact number of nines needed to cause failure varying dependi

[COMMITTERS] pgbulkload - pgbulkload: Split bulkload into bulkread and bulkwrite.

2009-05-01 Thread User Itagaki
Log Message: --- Split bulkload into bulkread and bulkwrite. They can be used sepalately. Modified Files: -- pgbulkload/include: pg_bulkload.h (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbulkload/pgbulkload/include/pg_bulkload.h.diff?r1=1.

[COMMITTERS] autodoc - autodoc: Another crack at 1.40

2009-05-01 Thread User Rbt
Log Message: --- Another crack at 1.40 Modified Files: -- autodoc: ChangeLog (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/ChangeLog.diff?r1=1.8&r2=1.9) -- Sent via pgsql-committers mailing list ([email protected]

[COMMITTERS] autodoc - autodoc: Finally, a 1.40 release changelog.

2009-05-01 Thread User Rbt
Log Message: --- Finally, a 1.40 release changelog. Modified Files: -- autodoc: ChangeLog (r1.11 -> r1.12) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/ChangeLog.diff?r1=1.11&r2=1.12) -- Sent via pgsql-committers mailing list (pgsql-commit

[COMMITTERS] autodoc - autodoc: make release was broken.

2009-05-01 Thread User Rbt
Log Message: --- make release was broken. Modified Files: -- autodoc: Makefile (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/Makefile.diff?r1=1.4&r2=1.5) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.

[COMMITTERS] autodoc - autodoc: Seems tar on FreeBSD has changed behaviour since the

2009-05-01 Thread User Rbt
Log Message: --- Seems tar on FreeBSD has changed behaviour since the last release. Copy files to new location and build tarball out of that directory. Modified Files: -- autodoc: ChangeLog (r1.10 -> r1.11) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/auto

[COMMITTERS] autodoc - autodoc: Tag for 1.40

2009-05-01 Thread User Rbt
Log Message: --- Tag for 1.40 Modified Files: -- autodoc: postgresql_autodoc.pl (r1.26 -> r1.27) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/postgresql_autodoc.pl.diff?r1=1.26&r2=1.27) -- Sent via pgsql-committers mailing list (pgsql-comm