| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Update minimum recovery point on truncation. |
| Date: | 2012-12-10 16:31:50 |
| Message-ID: | E1Ti6Gk-0002Mt-3U@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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,
minRecoveryPoint was not updated during recovery at all.
Branch
------
REL8_4_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/7e0d8d8457d922a63292c39862738969cac6c418
Modified Files
--------------
src/backend/access/transam/xact.c | 40 +++++++++++++++++++++++++++---------
src/backend/catalog/storage.c | 18 ++++++++++++++++
2 files changed, 48 insertions(+), 10 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-12-11 03:41:24 | pgsql: doc: Remove blastwave.org link |
| Previous Message | Heikki Linnakangas | 2012-12-10 16:31:49 | pgsql: Update minimum recovery point on truncation. |