[COMMITTERS] pgsql: Add notes that CREATE/DROP CONVERSION is similar to CREATE/DROP

2010-06-15 Thread Peter Eisentraut
Log Message: --- Add notes that CREATE/DROP CONVERSION is similar to CREATE/DROP TRANSLATION in the SQL standard. Modified Files: -- pgsql/doc/src/sgml/ref: create_conversion.sgml (r1.23 -> r1.24) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml

[COMMITTERS] pgsql: Refactor sprintf calls with computed format strings into multiple

2010-06-15 Thread Peter Eisentraut
Log Message: --- Refactor sprintf calls with computed format strings into multiple calls with constant format strings, so that the compiler can more easily check the formats for correctness. Modified Files: -- pgsql/src/backend/postmaster: postmaster.c (r1.611 -> r1

[COMMITTERS] pg-migrator - pg_migrator: getopt() returns 'int', not 'char'.

2010-06-15 Thread User Bmomjian
Log Message: --- getopt() returns 'int', not 'char'. Modified Files: -- pg_migrator/src: option.c (r1.34 -> r1.35) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pg-migrator/pg_migrator/src/option.c?r1=1.34&r2=1.35) -- Sent via pgsql-committers mailing list

[COMMITTERS] pgsql: Fix storage of getopt() return, should be 'int', for pg_upgrade.

2010-06-15 Thread Bruce Momjian
Log Message: --- Fix storage of getopt() return, should be 'int', for pg_upgrade. Steve Singer Modified Files: -- pgsql/contrib/pg_upgrade: option.c (r1.6 -> r1.7) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_upgrade/option.c?r1=1.6&r2=1.7)

[COMMITTERS] pgsql: Change the interpretation of the primary_key_attnums parameter of

2010-06-15 Thread Tom Lane
Log Message: --- Change the interpretation of the primary_key_attnums parameter of dblink_build_sql_insert() and related functions. Now the column numbers are treated as logical not physical column numbers. This will provide saner behavior in the presence of dropped columns; furthermore,

[COMMITTERS] pgsql: Clarify SELECT FOR UPDATE behavior in docs.

2010-06-15 Thread Bruce Momjian
Log Message: --- Clarify SELECT FOR UPDATE behavior in docs. Modified Files: -- pgsql/doc/src/sgml/ref: select.sgml (r1.130 -> r1.131) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/select.sgml?r1=1.130&r2=1.131) -- Sent via pgsql-commit

[COMMITTERS] pgsql: Remove hstore's text[] => text[] operator.

2010-06-15 Thread Robert Haas
Log Message: --- Remove hstore's text[] => text[] operator. This is not yet in any released version, so we still have the option to backtrack. Instead, document hstore(text[], text[]). Per discussion. Modified Files: -- pgsql/contrib/hstore: hstore.sql.in (r1.12

[COMMITTERS] pgsql: Fix dblink_build_sql_insert() and related functions to handle

2010-06-15 Thread Tom Lane
Log Message: --- Fix dblink_build_sql_insert() and related functions to handle dropped columns correctly. In passing, get rid of some dead logic in the underlying get_sql_insert() etc functions --- there is no caller that will pass null value-arrays to them. Per bug report from Robert Voi

[COMMITTERS] pgsql: Fix dblink_build_sql_insert() and related functions to handle

2010-06-15 Thread Tom Lane
Log Message: --- Fix dblink_build_sql_insert() and related functions to handle dropped columns correctly. In passing, get rid of some dead logic in the underlying get_sql_insert() etc functions --- there is no caller that will pass null value-arrays to them. Per bug report from Robert Voi

[COMMITTERS] pgsql: Fix dblink_build_sql_insert() and related functions to handle

2010-06-15 Thread Tom Lane
Log Message: --- Fix dblink_build_sql_insert() and related functions to handle dropped columns correctly. In passing, get rid of some dead logic in the underlying get_sql_insert() etc functions --- there is no caller that will pass null value-arrays to them. Per bug report from Robert Voi

[COMMITTERS] pgsql: Fix dblink_build_sql_insert() and related functions to handle

2010-06-15 Thread Tom Lane
Log Message: --- Fix dblink_build_sql_insert() and related functions to handle dropped columns correctly. In passing, get rid of some dead logic in the underlying get_sql_insert() etc functions --- there is no caller that will pass null value-arrays to them. Per bug report from Robert Voi

[COMMITTERS] pgsql: Fix dblink_build_sql_insert() and related functions to handle

2010-06-15 Thread Tom Lane
Log Message: --- Fix dblink_build_sql_insert() and related functions to handle dropped columns correctly. In passing, get rid of some dead logic in the underlying get_sql_insert() etc functions --- there is no caller that will pass null value-arrays to them. Per bug report from Robert Voi

[COMMITTERS] pgsql: Fix dblink_build_sql_insert() and related functions to handle

2010-06-15 Thread Tom Lane
Log Message: --- Fix dblink_build_sql_insert() and related functions to handle dropped columns correctly. In passing, get rid of some dead logic in the underlying get_sql_insert() etc functions --- there is no caller that will pass null value-arrays to them. Per bug report from Robert Voi

[COMMITTERS] pgsql: Fix dblink_build_sql_insert() and related functions to handle

2010-06-15 Thread Tom Lane
Log Message: --- Fix dblink_build_sql_insert() and related functions to handle dropped columns correctly. In passing, get rid of some dead logic in the underlying get_sql_insert() etc functions --- there is no caller that will pass null value-arrays to them. Per bug report from Robert Voi

[COMMITTERS] pgsql: Document new 9.0 behavior of ANALYZE on inheritance hierarchies.

2010-06-15 Thread Robert Haas
Log Message: --- Document new 9.0 behavior of ANALYZE on inheritance hierarchies. In particular, note that autovacuum does not yet understand that it might need to vacuum inheritance parents as a result of changes to the child tables. Modified Files: -- pgsql/doc/src/sgml/

[COMMITTERS] pgsql: Consolidate and improve checking of key-column-attnum arguments

2010-06-15 Thread Tom Lane
Log Message: --- Consolidate and improve checking of key-column-attnum arguments for dblink_build_sql_insert() and related functions. In particular, be sure to reject references to dropped and out-of-range column numbers. The numbers are still interpreted as physical column numbers, thoug

[COMMITTERS] pgsql: Consolidate and improve checking of key-column-attnum arguments

2010-06-15 Thread Tom Lane
Log Message: --- Consolidate and improve checking of key-column-attnum arguments for dblink_build_sql_insert() and related functions. In particular, be sure to reject references to dropped and out-of-range column numbers. The numbers are still interpreted as physical column numbers, thoug

[COMMITTERS] pgsql: Consolidate and improve checking of key-column-attnum arguments

2010-06-15 Thread Tom Lane
Log Message: --- Consolidate and improve checking of key-column-attnum arguments for dblink_build_sql_insert() and related functions. In particular, be sure to reject references to dropped and out-of-range column numbers. The numbers are still interpreted as physical column numbers, thoug

[COMMITTERS] pgsql: Consolidate and improve checking of key-column-attnum arguments

2010-06-15 Thread Tom Lane
Log Message: --- Consolidate and improve checking of key-column-attnum arguments for dblink_build_sql_insert() and related functions. In particular, be sure to reject references to dropped and out-of-range column numbers. The numbers are still interpreted as physical column numbers, thoug

[COMMITTERS] pgsql: Consolidate and improve checking of key-column-attnum arguments

2010-06-15 Thread Tom Lane
Log Message: --- Consolidate and improve checking of key-column-attnum arguments for dblink_build_sql_insert() and related functions. In particular, be sure to reject references to dropped and out-of-range column numbers. The numbers are still interpreted as physical column numbers, thoug

[COMMITTERS] pgsql: Consolidate and improve checking of key-column-attnum arguments

2010-06-15 Thread Tom Lane
Log Message: --- Consolidate and improve checking of key-column-attnum arguments for dblink_build_sql_insert() and related functions. In particular, be sure to reject references to dropped and out-of-range column numbers. The numbers are still interpreted as physical column numbers, thoug

[COMMITTERS] pgsql: Consolidate and improve checking of key-column-attnum arguments

2010-06-15 Thread Tom Lane
Log Message: --- Consolidate and improve checking of key-column-attnum arguments for dblink_build_sql_insert() and related functions. In particular, be sure to reject references to dropped and out-of-range column numbers. The numbers are still interpreted as physical column numbers, thoug

[COMMITTERS] pgsql: Unbreak MSVC builds for pg_archivecleanup by linking with

2010-06-15 Thread Andrew Dunstan
Log Message: --- Unbreak MSVC builds for pg_archivecleanup by linking with libpgport Modified Files: -- pgsql/src/tools/msvc: Mkvcbuild.pm (r1.57 -> r1.58) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/Mkvcbuild.pm?r1=1.57&r2=1.58) -- Sen

[COMMITTERS] pgsql: Add new GUC categories corresponding to sections in docs, and

2010-06-15 Thread Takahiro Itagaki
Log Message: --- Add new GUC categories corresponding to sections in docs, and move description for vacuum_defer_cleanup_age to the correct category. Sections in postgresql.conf are also sorted in the same order with docs. Per gripe by Fujii Masao, suggestion by Heikki Linnakangas, and pat