pgsql: Fix the torn-page hazard for PITR base backups by forcing full

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix the torn-page hazard for PITR base backups by forcing full
Date: 2006-04-17 18:55:05
Message-ID: 20060417185505.76C3911F6A98@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix the torn-page hazard for PITR base backups by forcing full page writes
to occur between pg_start_backup() and pg_stop_backup(), even if the GUC
setting full_page_writes is OFF. Per discussion, doing this in combination
with the already-existing checkpoint during pg_start_backup() should ensure
safety against partial page updates being included in the backup. We do
not have to force full page writes to occur during normal PITR operation,
as I had first feared.

Modified Files:
--------------
pgsql/src/backend/access/transam:
xlog.c (r1.235 -> r1.236)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.235&r2=1.236)

Browse pgsql-committers by date

  From Date Subject
Next Message User Nwakefield 2006-04-17 20:14:58 bizgres - bizgres:
Previous Message User Shachar 2006-04-17 18:28:19 oledb - oledb: Prepare version 1.0.0.20