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

From Vadim Mikheev
Subject Re: PITR, checkpoint, and local relations
Date
Msg-id 004801c23e98$39477290$ed2db841@home
Whole thread Raw
In response to Re: PITR, checkpoint, and local relations  ("J. R. Nield" <jrnield@usol.com>)
List 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




pgsql-hackers by date:

Previous
From: Greg Copeland
Date:
Subject: Another python patch -- minor
Next
From: Hannu Krosing
Date:
Subject: Re: Open 7.3 items