Re: Point in Time Recovery - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Point in Time Recovery
Date
Msg-id 200407132301.i6DN1fb16205@candle.pha.pa.us
Whole thread Raw
In response to Re: Point in Time Recovery  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Point in Time Recovery  (Simon Riggs <simon@2ndquadrant.com>)
Re: Point in Time Recovery  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > So the situation is: 
> > - You must only stop recovery at a point in time (in the logs) after the
> > backup had completed.
> 
> Right.
> 
> > No way to enforce that currently, apart from procedurally. Not exactly
> > frequent, so I think I just document that and move on, eh?
> 
> The procedure that generates a backup has got to be responsible for
> recording both the start and stop times.  If it does not do so then
> it's fatally flawed.  (Note also that you had better be careful to get
> the time as seen on the server machine's clock ... this could be a nasty
> gotcha if the backup is run on a different machine, such as an NFS
> server.)

OK, but procedurally, how do you correlate the start/stop time of the
tar backup with the WAL numeric file names?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Is "trust" really a good default?
Next
From: Simon Riggs
Date:
Subject: Re: Point in Time Recovery