From: Simon Riggs <simon@2ndquadrant.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Point in Time Recovery
Date: Tue, 13 Jul 2004 23:52:34 +0100
Message-ID: <1089759153.17493.3270.camel@stromboli> (raw)
In-Reply-To: <200407132242.i6DMgg612564@candle.pha.pa.us>
References: <200407132242.i6DMgg612564@candle.pha.pa.us>
On Tue, 2004-07-13 at 23:42, Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Tue, 2004-07-13 at 22:19, Tom Lane wrote:
> >
> > > To have a consistent recovery at all, you must replay the log starting
> > > from a checkpoint before the backup began and extending to the time that
> > > the backup finished. You only get to decide where to stop after that
> > > point.
> > >
> >
> > So the situation is:
> > - You must only stop recovery at a point in time (in the logs) after the
> > backup had completed.
> >
> > No way to enforce that currently, apart from procedurally. Not exactly
> > frequent, so I think I just document that and move on, eh?
>
> If it happens, could you use your previous full backup and the PITR logs
> from before stop stopped logging, and then after?
Yes.
> Is there a period
> where they could not restore reliably?
Good question. No is the answer.
The situation is that the backup isn't timestamped with respect to the
logs, so its possible to attempt to use the wrong backup for recovery.
The solution is procedural - make sure you timestamp your backup files,
so you know which ones to recover with...
Best Regards, Simon Riggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: simon@2ndquadrant.com, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: Point in Time Recovery
In-Reply-To: <1089759153.17493.3270.camel@stromboli>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox