[COMMITTERS] pgsql: Fix pg_upgrade -O/-o options

Fix pg_upgrade -O/-o options Fix previous commit that added synchronous_commit=off, but broke -O/-o due to missing space in argument passing. Backpatch to 9.2. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/acdb8c225955bbf582bb050e6217f79493f031eb Modified Files -

[COMMITTERS] pgsql: Fix pg_upgrade -O/-o options

Fix pg_upgrade -O/-o options Fix previous commit that added synchronous_commit=off, but broke -O/-o due to missing space in argument passing. Backpatch to 9.2. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/35fb1434b185c5e9ee1e232f3349713201e7cbfa Modified

[COMMITTERS] pgsql: doc: Remove blastwave.org link

doc: Remove blastwave.org link Apparently, this service has been dead since 2008. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/8e48d77cab8483fb381db9051225b46a0e4c2bc2 Modified Files -- doc/src/sgml/installation.sgml |4 ++-- 1 files changed, 2 ins

[COMMITTERS] pgsql: Update minimum recovery point on truncation.

Update minimum recovery point on truncation. If a file is truncated, we must update minRecoveryPoint. Once a file is truncated, there's no going back; it would not be safe to stop recovery at a point earlier than that anymore. Per report from Kyotaro HORIGUCHI. Backpatch to 8.4. Before that, minR

[COMMITTERS] pgsql: Update minimum recovery point on truncation.

Update minimum recovery point on truncation. If a file is truncated, we must update minRecoveryPoint. Once a file is truncated, there's no going back; it would not be safe to stop recovery at a point earlier than that anymore. Per report from Kyotaro HORIGUCHI. Backpatch to 8.4. Before that, minR

[COMMITTERS] pgsql: Update minimum recovery point on truncation.

Update minimum recovery point on truncation. If a file is truncated, we must update minRecoveryPoint. Once a file is truncated, there's no going back; it would not be safe to stop recovery at a point earlier than that anymore. Per report from Kyotaro HORIGUCHI. Backpatch to 8.4. Before that, minR

[COMMITTERS] pgsql: Update minimum recovery point on truncation.

Update minimum recovery point on truncation. If a file is truncated, we must update minRecoveryPoint. Once a file is truncated, there's no going back; it would not be safe to stop recovery at a point earlier than that anymore. Per report from Kyotaro HORIGUCHI. Backpatch to 8.4. Before that, minR

[COMMITTERS] pgsql: Update minimum recovery point on truncation.

Update minimum recovery point on truncation. If a file is truncated, we must update minRecoveryPoint. Once a file is truncated, there's no going back; it would not be safe to stop recovery at a point earlier than that anymore. Per report from Kyotaro HORIGUCHI. Backpatch to 8.4. Before that, minR

[COMMITTERS] pgsql: Fix the tracking of min recovery point timeline.

Fix the tracking of min recovery point timeline. Forgot to update it at the right place. Also, consider checkpoint record that switches to new timelne to be on the new timeline. This fixes erroneous "requested timeline 2 does not contain minimum recovery point" errors, pointed out by Amit Kapila