[COMMITTERS] pgsql: pg_upgrade: document use of file system and COW snapshots

2014-02-12 Thread Bruce Momjian
pg_upgrade: document use of file system and COW snapshots Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/bcec58cf1ebf20ea237be042d3ef774f887557a9 Modified Files -- doc/src/sgml/pgupgrade.sgml |5 - 1 file changed, 4 insertions(+), 1 deletion(-)

[COMMITTERS] pgsql: Improve cross-references between minor version release notes.

2014-02-12 Thread Tom Lane
Improve cross-references between minor version release notes. We have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're

[COMMITTERS] pgsql: Improve cross-references between minor version release notes.

2014-02-12 Thread Tom Lane
Improve cross-references between minor version release notes. We have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're

[COMMITTERS] pgsql: Improve cross-references between minor version release notes.

2014-02-12 Thread Tom Lane
Improve cross-references between minor version release notes. We have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're

[COMMITTERS] pgsql: Improve cross-references between minor version release notes.

2014-02-12 Thread Tom Lane
Improve cross-references between minor version release notes. We have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're

[COMMITTERS] pgsql: Improve cross-references between minor version release notes.

2014-02-12 Thread Tom Lane
Improve cross-references between minor version release notes. We have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're

[COMMITTERS] pgsql: Improve cross-references between minor version release notes.

2014-02-12 Thread Tom Lane
Improve cross-references between minor version release notes. We have a practice of providing a "bread crumb" trail between the minor versions where the migration section actually tells you to do something. Historically that was just plain text, eg, "see the release notes for 9.2.4"; but if you're

[COMMITTERS] pgsql: Improve text of stub HISTORY file.

2014-02-12 Thread Tom Lane
Improve text of stub HISTORY file. Per Peter Eisentraut. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/c90859fd761a24abc5fe4109514827bdf559099b Modified Files -- HISTORY |7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) -- Sent v

[COMMITTERS] pgsql: Improve text of stub HISTORY file.

2014-02-12 Thread Tom Lane
Improve text of stub HISTORY file. Per Peter Eisentraut. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/ed2803bdb94b9b8ad80f0d9cdb5976345a0d2fdb Modified Files -- HISTORY |7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) -- Sent v

[COMMITTERS] pgsql: Improve text of stub HISTORY file.

2014-02-12 Thread Tom Lane
Improve text of stub HISTORY file. Per Peter Eisentraut. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/6fd1fd53c5671253804d5af33a2092d36a46f1fa Modified Files -- HISTORY |7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) -- Sent v

[COMMITTERS] pgsql: Improve text of stub HISTORY file.

2014-02-12 Thread Tom Lane
Improve text of stub HISTORY file. Per Peter Eisentraut. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/4f33f039699bdd0e47ca0a2e7bc8158d02388684 Modified Files -- HISTORY |7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) -- Sent v

[COMMITTERS] pgsql: Improve text of stub HISTORY file.

2014-02-12 Thread Tom Lane
Improve text of stub HISTORY file. Per Peter Eisentraut. Branch -- REL8_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/e99754adbc2170a31ea8df467d56c9ed40ee463f Modified Files -- HISTORY |8 1 file changed, 4 insertions(+), 4 deletions(-) -- Sent

[COMMITTERS] pgsql: Improve text of stub HISTORY file.

2014-02-12 Thread Tom Lane
Improve text of stub HISTORY file. Per Peter Eisentraut. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/dea5a8c402b11819a24a06f1e110c371a908d359 Modified Files -- HISTORY |7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) -- Sent via pgsq

[COMMITTERS] pgsql: Improve libpq's error recovery for connection loss during COPY.

2014-02-12 Thread Tom Lane
Improve libpq's error recovery for connection loss during COPY. In pqSendSome, if the connection is already closed at entry, discard any queued output data before returning. There is no possibility of ever sending the data, and anyway this corresponds to what we'd do if we'd detected a hard error

[COMMITTERS] pgsql: Improve libpq's error recovery for connection loss during COPY.

2014-02-12 Thread Tom Lane
Improve libpq's error recovery for connection loss during COPY. In pqSendSome, if the connection is already closed at entry, discard any queued output data before returning. There is no possibility of ever sending the data, and anyway this corresponds to what we'd do if we'd detected a hard error

[COMMITTERS] pgsql: Improve libpq's error recovery for connection loss during COPY.

2014-02-12 Thread Tom Lane
Improve libpq's error recovery for connection loss during COPY. In pqSendSome, if the connection is already closed at entry, discard any queued output data before returning. There is no possibility of ever sending the data, and anyway this corresponds to what we'd do if we'd detected a hard error

[COMMITTERS] pgsql: Improve libpq's error recovery for connection loss during COPY.

2014-02-12 Thread Tom Lane
Improve libpq's error recovery for connection loss during COPY. In pqSendSome, if the connection is already closed at entry, discard any queued output data before returning. There is no possibility of ever sending the data, and anyway this corresponds to what we'd do if we'd detected a hard error

[COMMITTERS] pgsql: Improve libpq's error recovery for connection loss during COPY.

2014-02-12 Thread Tom Lane
Improve libpq's error recovery for connection loss during COPY. In pqSendSome, if the connection is already closed at entry, discard any queued output data before returning. There is no possibility of ever sending the data, and anyway this corresponds to what we'd do if we'd detected a hard error

[COMMITTERS] pgsql: Improve libpq's error recovery for connection loss during COPY.

2014-02-12 Thread Tom Lane
Improve libpq's error recovery for connection loss during COPY. In pqSendSome, if the connection is already closed at entry, discard any queued output data before returning. There is no possibility of ever sending the data, and anyway this corresponds to what we'd do if we'd detected a hard error

[COMMITTERS] pgsql: Revert gmake/make release note changes

2014-02-12 Thread Bruce Momjian
Revert gmake/make release note changes Backbranch release note changes cause merge conflicts. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/993c3961a4166a766c9b0a67701e9c82432550cc Modified Files -- doc/src/sgml/release-8.3.sgml |2 +- doc/src/sgml/

[COMMITTERS] pgsql: Rename 'gmake' to 'make' in docs and recommended commands

2014-02-12 Thread Bruce Momjian
Rename 'gmake' to 'make' in docs and recommended commands This simplifies the docs and makes it easier to cut/paste command lines. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/2fc80e8e8304913c8dd1090bb2976632c0f4a8c3 Modified Files -- contrib/README

[COMMITTERS] pgsql: pg_upgrade: dramatically reduce memory consumption

2014-02-12 Thread Bruce Momjian
pg_upgrade: dramatically reduce memory consumption Report from Jeff Janes Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/2a2e40d6d9d8a2c6a61817542a2d8c369935 Modified Files -- contrib/pg_upgrade/check.c | 14 contrib/pg_upgrade/info.c

[COMMITTERS] pgsql: pg_test_fsync: add C comment about direct I/O and write size fai

2014-02-12 Thread Bruce Momjian
pg_test_fsync: add C comment about direct I/O and write size failure Report from Marti Raudsepp Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f9bb944cd879949cf454b941f2b8fa7b00fcc1e4 Modified Files -- contrib/pg_test_fsync/pg_test_fsync.c |6 ++

[COMMITTERS] pgsql: In XLogReadBufferExtended, don't assume P_NEW yields consecutive

2014-02-12 Thread Tom Lane
In XLogReadBufferExtended, don't assume P_NEW yields consecutive pages. In a database that's not yet reached consistency, it's possible that some segments of a relation are not full-size but are not the last ones either. Because of the way smgrnblocks() works, asking for a new page with P_NEW will

[COMMITTERS] pgsql: In XLogReadBufferExtended, don't assume P_NEW yields consecutive

2014-02-12 Thread Tom Lane
In XLogReadBufferExtended, don't assume P_NEW yields consecutive pages. In a database that's not yet reached consistency, it's possible that some segments of a relation are not full-size but are not the last ones either. Because of the way smgrnblocks() works, asking for a new page with P_NEW will

[COMMITTERS] pgsql: In XLogReadBufferExtended, don't assume P_NEW yields consecutive

2014-02-12 Thread Tom Lane
In XLogReadBufferExtended, don't assume P_NEW yields consecutive pages. In a database that's not yet reached consistency, it's possible that some segments of a relation are not full-size but are not the last ones either. Because of the way smgrnblocks() works, asking for a new page with P_NEW will

[COMMITTERS] pgsql: In XLogReadBufferExtended, don't assume P_NEW yields consecutive

2014-02-12 Thread Tom Lane
In XLogReadBufferExtended, don't assume P_NEW yields consecutive pages. In a database that's not yet reached consistency, it's possible that some segments of a relation are not full-size but are not the last ones either. Because of the way smgrnblocks() works, asking for a new page with P_NEW will

[COMMITTERS] pgsql: In XLogReadBufferExtended, don't assume P_NEW yields consecutive

2014-02-12 Thread Tom Lane
In XLogReadBufferExtended, don't assume P_NEW yields consecutive pages. In a database that's not yet reached consistency, it's possible that some segments of a relation are not full-size but are not the last ones either. Because of the way smgrnblocks() works, asking for a new page with P_NEW will

[COMMITTERS] pgsql: In XLogReadBufferExtended, don't assume P_NEW yields consecutive

2014-02-12 Thread Tom Lane
In XLogReadBufferExtended, don't assume P_NEW yields consecutive pages. In a database that's not yet reached consistency, it's possible that some segments of a relation are not full-size but are not the last ones either. Because of the way smgrnblocks() works, asking for a new page with P_NEW will

[COMMITTERS] pgsql: Add missing include, required on some platforms

2014-02-12 Thread Magnus Hagander
Add missing include, required on some platforms Noted by the buildfarm and Andres Freund Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/48870dd9f752db7f953dde54b3d16e82d529e0db Modified Files -- src/bin/pg_basebackup/pg_basebackup.c |1 + 1 file chan

[COMMITTERS] pgsql: Add missing include, required on some platforms

2014-02-12 Thread Magnus Hagander
Add missing include, required on some platforms Noted by the buildfarm and Andres Freund Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/efb425a6f767da9447403d83f8ceb089ded3959d Modified Files -- src/bin/pg_basebackup/pg_basebackup.c |1 + 1 fi

[COMMITTERS] pgsql: Add missing include, required on some platforms

2014-02-12 Thread Magnus Hagander
Add missing include, required on some platforms Noted by the buildfarm and Andres Freund Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/ca7435033bee9a58bbee27b1fd18b7fac0a94e14 Modified Files -- src/bin/pg_basebackup/pg_basebackup.c |1 + 1 fi

Re: [COMMITTERS] pgsql: Kill pg_basebackup background process when exiting

2014-02-12 Thread Magnus Hagander
On Wed, Feb 12, 2014 at 7:47 PM, Andres Freund wrote: > > On 2014-02-12 17:46:48 +, Magnus Hagander wrote: > > Kill pg_basebackup background process when exiting > > > > If an error occurs in the foreground (backup) process of pg_basebackup, > > and we exit in a controlled way, the background

Re: [COMMITTERS] pgsql: Kill pg_basebackup background process when exiting

2014-02-12 Thread Andres Freund
Hi Magnus, On 2014-02-12 17:46:48 +, Magnus Hagander wrote: > Kill pg_basebackup background process when exiting > > If an error occurs in the foreground (backup) process of pg_basebackup, > and we exit in a controlled way, the background process (streaming > xlog process) would stay around a

[COMMITTERS] pgsql: Kill pg_basebackup background process when exiting

2014-02-12 Thread Magnus Hagander
Kill pg_basebackup background process when exiting If an error occurs in the foreground (backup) process of pg_basebackup, and we exit in a controlled way, the background process (streaming xlog process) would stay around and keep streaming. Branch -- REL9_3_STABLE Details --- http://git

[COMMITTERS] pgsql: Kill pg_basebackup background process when exiting

2014-02-12 Thread Magnus Hagander
Kill pg_basebackup background process when exiting If an error occurs in the foreground (backup) process of pg_basebackup, and we exit in a controlled way, the background process (streaming xlog process) would stay around and keep streaming. Branch -- REL9_2_STABLE Details --- http://git

[COMMITTERS] pgsql: Kill pg_basebackup background process when exiting

2014-02-12 Thread Magnus Hagander
Kill pg_basebackup background process when exiting If an error occurs in the foreground (backup) process of pg_basebackup, and we exit in a controlled way, the background process (streaming xlog process) would stay around and keep streaming. Branch -- master Details --- http://git.postgr

[COMMITTERS] pgsql: Use --disable-auto-import linker switch in Mingw builds, too.

2014-02-12 Thread Tom Lane
Use --disable-auto-import linker switch in Mingw builds, too. This is evidently the default on buildfarm member narwhal, but that is a pretty ancient Mingw version, and there is reason to think that more recent versions of GNU ld have this feature turned on by default. Since we are trying to achie

[COMMITTERS] pgsql: Remove --enable-auto-import linker switch in Cygwin build.

2014-02-12 Thread Tom Lane
Remove --enable-auto-import linker switch in Cygwin build. This is expected to make it start failing when contrib modules reference non-PGDLLIMPORT'ed global variables, as the other Windows build methods do. Aside from the value of consistency, the underlying implementation of this switch is pret

[COMMITTERS] pgsql: doc: Postgres date-style date-only output is ISO

2014-02-12 Thread Bruce Momjian
doc: Postgres date-style date-only output is ISO Backpatch to 9.3 Report from MauMau Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/8c9db4a5a4b5e8fe1142b1ea6659b225b7641a76 Modified Files -- doc/src/sgml/datatype.sgml |6 -- 1 file changed, 4 in

[COMMITTERS] pgsql: doc: Postgres date-style date-only output is ISO

2014-02-12 Thread Bruce Momjian
doc: Postgres date-style date-only output is ISO Backpatch to 9.3 Report from MauMau Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/8247236c639d08724ed13104c2acf8b322a735f0 Modified Files -- doc/src/sgml/datatype.sgml |6 -- 1 file change

[COMMITTERS] pgsql: Tweak position of $(DLL_DEFFILE) in shared-library link commands

2014-02-12 Thread Tom Lane
Tweak position of $(DLL_DEFFILE) in shared-library link commands. Reading the GNU ld man page suggests that this is order-sensitive and should go in front of library references. Correction to commit 846e91e0223cf9f2821c3ad4dfbb929cb027. Branch -- master Details --- http://git.postgr