[COMMITTERS] pgsql: have pg_regress fall back on testing with the canonical results
Log Message: --- have pg_regress fall back on testing with the canonical results file if an alternative test is specified but none succeeds. Modified Files: -- pgsql/src/test/regress: pg_regress.c (r1.17 -> r1.18) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/pg_regress.c.diff?r1=1.17&r2=1.18) ---(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] pgsql: Remove extra argument to printf().
Log Message: --- Remove extra argument to printf(). Modified Files: -- pgsql/src/test/regress: pg_regress.c (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/pg_regress.c.diff?r1=1.18&r2=1.19) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Allow multiple -n (schema) and -t (table) pg_dump options, and
Log Message: --- Allow multiple -n (schema) and -t (table) pg_dump options, and add -T and -N options to exclude objects. Also support regular expressions for option object names. Greg Sabino Mullane Modified Files: -- pgsql/doc/src/sgml/ref: pg_dump.sgml (r1.86 -> r1.87) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_dump.sgml.diff?r1=1.86&r2=1.87) pgsql/src/bin/pg_dump: common.c (r1.91 -> r1.92) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/common.c.diff?r1=1.91&r2=1.92) pg_dump.c (r1.442 -> r1.443) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c.diff?r1=1.442&r2=1.443) pg_dump.h (r1.127 -> r1.128) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.h.diff?r1=1.127&r2=1.128) ---(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
[COMMITTERS] pgsql: Done: < o %Allow pg_dump to use multiple -t and -n switches
Log Message: --- Done: < o %Allow pg_dump to use multiple -t and -n switches [pg_dump] < < http://archives.postgresql.org/pgsql-patches/2006-01/msg00190.php < > o -Allow pg_dump to use multiple -t and -n switches, exclusion > ability, and regular expression object matching Modified Files: -- pgsql/doc: TODO (r1.1929 -> r1.1930) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1929&r2=1.1930) pgsql/doc/src/FAQ: TODO.html (r1.432 -> r1.433) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.432&r2=1.433) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Remove TODO.detail/pg_dump.
Log Message: --- Remove TODO.detail/pg_dump. Removed Files: - pgsql/doc/TODO.detail: pg_dump (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/pg_dump) ---(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
[COMMITTERS] pgsql: Add pg_dump -X no-data-for-failed-tables option to suppress
Log Message: --- Add pg_dump -X no-data-for-failed-tables option to suppress loading data if table creation failed (the table already exists). Martin Pitt Modified Files: -- pgsql/doc/src/sgml/ref: pg_restore.sgml (r1.59 -> r1.60) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_restore.sgml.diff?r1=1.59&r2=1.60) pgsql/src/bin/pg_dump: pg_backup.h (r1.41 -> r1.42) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup.h.diff?r1=1.41&r2=1.42) pg_backup_archiver.c (r1.134 -> r1.135) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_archiver.c.diff?r1=1.134&r2=1.135) pg_restore.c (r1.79 -> r1.80) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_restore.c.diff?r1=1.79&r2=1.80) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Add support for loadable modules to allocated shared memory and
Log Message: --- Add support for loadable modules to allocated shared memory and lightweight locks. Marc Munro Modified Files: -- pgsql/src/backend/storage/ipc: ipci.c (r1.86 -> r1.87) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/ipci.c.diff?r1=1.86&r2=1.87) shmem.c (r1.94 -> r1.95) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/shmem.c.diff?r1=1.94&r2=1.95) pgsql/src/backend/storage/lmgr: lwlock.c (r1.42 -> r1.43) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lwlock.c.diff?r1=1.42&r2=1.43) pgsql/src/include/storage: lwlock.h (r1.30 -> r1.31) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/lwlock.h.diff?r1=1.30&r2=1.31) pg_shmem.h (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/pg_shmem.h.diff?r1=1.18&r2=1.19) shmem.h (r1.47 -> r1.48) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/shmem.h.diff?r1=1.47&r2=1.48) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Editorialize a bit on the recent patch, reverting to the original
Log Message: --- Editorialize a bit on the recent patch, reverting to the original versions of the text where appropiate. Modified Files: -- pgsql/doc/src/sgml: maintenance.sgml (r1.57 -> r1.58) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/maintenance.sgml.diff?r1=1.57&r2=1.58) external-projects.sgml (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/external-projects.sgml.diff?r1=1.11&r2=1.12) ---(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
[COMMITTERS] pgsql: Fix bug I introduced while cleaning up pg_dump -t/-n patch.
Log Message: --- Fix bug I introduced while cleaning up pg_dump -t/-n patch. Modified Files: -- pgsql/src/bin/pg_dump: pg_dump.c (r1.443 -> r1.444) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c.diff?r1=1.443&r2=1.444) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Add support for multi-row VALUES clauses as part of INSERT
Log Message: --- Add support for multi-row VALUES clauses as part of INSERT statements (e.g. "INSERT ... VALUES (...), (...), ...") and elsewhere as allowed by the spec. (e.g. similar to a FROM clause subselect). initdb required. Joe Conway and Tom Lane. Modified Files: -- pgsql/src/backend/catalog: heap.c (r1.311 -> r1.312) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/heap.c.diff?r1=1.311&r2=1.312) pgsql/src/backend/commands: explain.c (r1.149 -> r1.150) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/explain.c.diff?r1=1.149&r2=1.150) pgsql/src/backend/executor: Makefile (r1.23 -> r1.24) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/Makefile.diff?r1=1.23&r2=1.24) execAmi.c (r1.88 -> r1.89) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execAmi.c.diff?r1=1.88&r2=1.89) execProcnode.c (r1.57 -> r1.58) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execProcnode.c.diff?r1=1.57&r2=1.58) pgsql/src/backend/nodes: copyfuncs.c (r1.344 -> r1.345) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c.diff?r1=1.344&r2=1.345) equalfuncs.c (r1.278 -> r1.279) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c.diff?r1=1.278&r2=1.279) outfuncs.c (r1.279 -> r1.280) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/outfuncs.c.diff?r1=1.279&r2=1.280) print.c (r1.80 -> r1.81) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/print.c.diff?r1=1.80&r2=1.81) readfuncs.c (r1.192 -> r1.193) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/readfuncs.c.diff?r1=1.192&r2=1.193) pgsql/src/backend/optimizer/path: allpaths.c (r1.149 -> r1.150) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/allpaths.c.diff?r1=1.149&r2=1.150) costsize.c (r1.164 -> r1.165) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/costsize.c.diff?r1=1.164&r2=1.165) pgsql/src/backend/optimizer/plan: createplan.c (r1.215 -> r1.216) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/createplan.c.diff?r1=1.215&r2=1.216) planner.c (r1.205 -> r1.206) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planner.c.diff?r1=1.205&r2=1.206) setrefs.c (r1.122 -> r1.123) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/setrefs.c.diff?r1=1.122&r2=1.123) subselect.c (r1.110 -> r1.111) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/subselect.c.diff?r1=1.110&r2=1.111) pgsql/src/backend/optimizer/util: clauses.c (r1.215 -> r1.216) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.215&r2=1.216) pathnode.c (r1.131 -> r1.132) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/pathnode.c.diff?r1=1.131&r2=1.132) plancat.c (r1.122 -> r1.123) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/plancat.c.diff?r1=1.122&r2=1.123) relnode.c (r1.80 -> r1.81) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/relnode.c.diff?r1=1.80&r2=1.81) pgsql/src/backend/parser: analyze.c (r1.340 -> r1.341) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c.diff?r1=1.340&r2=1.341) gram.y (r2.553 -> r2.554) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.553&r2=2.554) parse_expr.c (r1.195 -> r1.196) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c.diff?r1=1.195&r2=1.196) parse_node.c (r1.93 -> r1.94) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_node.c.diff?r1=1.93&r2=1.94) parse_relation.c (r1.123 -> r1.124) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_relation.c.diff?r1=1.123&r2=1.124) parse_target.c (r1.146 -> r1.147) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_target.c.diff?r1=1.146&r2=1.147) parse_type.c (r1.82 -> r1.83) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_type.c.diff?r1=1.82&r2=1.83) pgsql/src/backend/rewrite: rewriteHandler.c (r1.164 -> r1.165) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/rewrite/rewriteHandler.c.diff?r1=1.164&r2=1.165) pgsql/src/backend/utils/adt: ruleutils.c (r1.229 -> r1.230) (http://develop
[COMMITTERS] pgsql: Done: o -Allow INSERT INTO tab (col1, ..) VALUES (val1,
Log Message: --- Done: o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) Modified Files: -- pgsql/doc: TODO (r1.1930 -> r1.1931) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1930&r2=1.1931) pgsql/doc/src/FAQ: TODO.html (r1.433 -> r1.434) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.433&r2=1.434) ---(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
