[COMMITTERS] pgsql: Remove use of obsolescent Autoconf macros

Remove use of obsolescent Autoconf macros Remove the use of the following macros, which are obsolescent according to the Autoconf documentation: - AC_C_CONST - AC_C_STRINGIZE - AC_C_VOLATILE - AC_FUNC_MEMCMP Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/34fa72ec9c

[COMMITTERS] pgsql: Prevent possible compiler warnings.

Prevent possible compiler warnings. Back-patch commit a3e8486dffc413506b14eae9dc5d423f6ae8324a into the 9.0 branch. This is the only warning I'm seeing in the live branches with gcc 4.4.7 (other than the known "unused variable 'yyg'" flex lossage), which makes it just annoying enough to want to c

[COMMITTERS] pgsql: Fix pg_dumpall to work for databases flagged as read-only.

Fix pg_dumpall to work for databases flagged as read-only. pg_dumpall's charter is to be able to recreate a database cluster's contents in a virgin installation, but it was failing to honor that contract if the cluster had any ALTER DATABASE SET default_transaction_read_only settings. By includin

[COMMITTERS] pgsql: Fix pg_dumpall to work for databases flagged as read-only.

Fix pg_dumpall to work for databases flagged as read-only. pg_dumpall's charter is to be able to recreate a database cluster's contents in a virgin installation, but it was failing to honor that contract if the cluster had any ALTER DATABASE SET default_transaction_read_only settings. By includin

[COMMITTERS] pgsql: Fix pg_dumpall to work for databases flagged as read-only.

Fix pg_dumpall to work for databases flagged as read-only. pg_dumpall's charter is to be able to recreate a database cluster's contents in a virgin installation, but it was failing to honor that contract if the cluster had any ALTER DATABASE SET default_transaction_read_only settings. By includin

[COMMITTERS] pgsql: Fix pg_dumpall to work for databases flagged as read-only.

Fix pg_dumpall to work for databases flagged as read-only. pg_dumpall's charter is to be able to recreate a database cluster's contents in a virgin installation, but it was failing to honor that contract if the cluster had any ALTER DATABASE SET default_transaction_read_only settings. By includin

[COMMITTERS] pgsql: Fix pg_dumpall to work for databases flagged as read-only.

Fix pg_dumpall to work for databases flagged as read-only. pg_dumpall's charter is to be able to recreate a database cluster's contents in a virgin installation, but it was failing to honor that contract if the cluster had any ALTER DATABASE SET default_transaction_read_only settings. By includin

[COMMITTERS] pgsql: Fix pg_dumpall to work for databases flagged as read-only.

Fix pg_dumpall to work for databases flagged as read-only. pg_dumpall's charter is to be able to recreate a database cluster's contents in a virgin installation, but it was failing to honor that contract if the cluster had any ALTER DATABASE SET default_transaction_read_only settings. By includin

[COMMITTERS] pgsql: pg_upgrade: Handle default_transaction_read_only settings

pg_upgrade: Handle default_transaction_read_only settings Setting default_transaction_read_only=true could prevent pg_upgrade from completing, so prepend default_transaction_read_only=false to PGOPTIONS. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/e7d56aee2d1805

[COMMITTERS] pgsql: Editorial corrections to the October 2013 minor-release notes.

Editorial corrections to the October 2013 minor-release notes. This is mostly to fix incorrect migration instructions: since the preceding minor releases advised reindexing some GIST indexes, it's important that we back-link to that advice rather than earlier instances. Also improve some bug desc