From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Point in Time Recovery
Date: Tue, 13 Jul 2004 18:56:31 -0400
Message-ID: <19894.1089759391@sss.pgh.pa.us> (raw)
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>
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
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: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, pgsql-hackers@postgresql.org
Subject: Re: Point in Time Recovery
In-Reply-To: <19894.1089759391@sss.pgh.pa.us>
* 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