To: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Point in Time Recovery 
In-reply-to: <1089757534.17493.3217.camel@stromboli> 
References: <1089060299.17493.58.camel@stromboli>
	<4263.1089064016@sss.pgh.pa.us>
	<1089150005.17493.270.camel@stromboli>
	<1089718702.17493.2527.camel@stromboli>
	<15780.1089728984@sss.pgh.pa.us>
	<1089750349.17493.3092.camel@stromboli>
	<18739.1089753596@sss.pgh.pa.us>
	<1089757534.17493.3217.camel@stromboli>
Comments: In-reply-to Simon Riggs <simon@2ndquadrant.com>
	message dated "Tue, 13 Jul 2004 23:25:34 +0100"
Date: Tue, 13 Jul 2004 18:56:31 -0400
Message-ID: <19894.1089759391@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

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.)

			regards, tom lane