Re: PITR, checkpoint, and local relations - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject Re: PITR, checkpoint, and local relations
Date
Msg-id 3705826352029646A3E91C53F7189E325185D9@sectorbase2.sectorbase.com
Whole thread Raw
In response to PITR, checkpoint, and local relations  ("J. R. Nield" <jrnield@usol.com>)
Responses Re: PITR, checkpoint, and local relations  (Richard Tucker <richt@multera.com>)
List pgsql-hackers
> > > As long as whole block is saved in log on first after
> > > checkpoint (you made before backup) change to block.
> >
> I thought half the point of PITR was to be able to
> turn off pre-image logging so you can trade potential
> recovery time for speed without fear of data-loss.
> Didn't we have this discussion before?

> Suppose you can turn off/on PostgreSQL's atomic write on
> the fly.  Which means turning on or off whether XLoginsert
> writes a copy of the block into the log file upon first
> modification after a checkpoint.
> So ALTER SYSTEM BEGIN BACKUP would turn on atomic write
> and then checkpoint the database.
> So while the OS copy of the data files is going on the
> atomic write would be enabled. So any read of a partial
> write would be fixed up by the usual crash recovery mechanism.

Yes, simple way to satisfy everyone.

Vadim


pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: Re: PITR, checkpoint, and local relations
Next
From: "J. R. Nield"
Date:
Subject: Re: PITR, checkpoint, and local relations