| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'richt(at)multera(dot)com'" <richt(at)multera(dot)com>, "J(dot) R(dot) Nield" <jrnield(at)usol(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PITR, checkpoint, and local relations |
| Date: | 2002-08-02 22:15:32 |
| Message-ID: | 3705826352029646A3E91C53F7189E325185D9@sectorbase2.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J. R. Nield | 2002-08-02 22:24:07 | Re: PITR, checkpoint, and local relations |
| Previous Message | Mikheev, Vadim | 2002-08-02 22:01:11 | Re: PITR, checkpoint, and local relations |