Re: PITR, checkpoint, and local relations
Vadim Mikheev <vmikheev@sectorbase.com>
From: "Vadim Mikheev" <vmikheev@sectorbase.com>
To: "J. R. Nield" <jrnield@usol.com>, "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "Richard Tucker" <richt@multera.com>, "Bruce Momjian" <pgman@candle.pha.pa.us>, "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>, "PostgreSQL Hacker" <pgsql-hackers@postgresql.org>
Date: 2002-08-08T04:58:19Z
Lists: pgsql-hackers
> > The xlog code must allow us to force an advance to the next log file, > > and truncate the archived file when it's copied so as not to waste > > space. > > Uh, why? Why not just force a checkpoint and remember the exact > location of the checkpoint within the current log file? Yes, why not just save pg_control' content with new checkpoint position in it? Didn't we agree (or at least I don't remember objections to Tom' suggestion) that backup will not save log files at all and that this will be task of log archiving procedure? Even if we are going to reconsider this approach, I would just save required portion of log at *this moment* and do that space optimization *later*. Vadim