| From: | "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> |
|---|---|
| To: | "J(dot) R(dot) Nield" <jrnield(at)usol(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Richard Tucker" <richt(at)multera(dot)com>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "PostgreSQL Hacker" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PITR, checkpoint, and local relations |
| Date: | 2002-08-08 04:58:19 |
| Message-ID: | 004801c23e98$39477290$ed2db841@home |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-08 05:06:47 | Re: stand-alone composite types patch (was [HACKERS] Proposal: |
| Previous Message | Tom Lane | 2002-08-08 04:55:22 | Re: stand-alone composite types patch (was [HACKERS] Proposal: stand-alone composite types) |