Re: Point in Time Recovery

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Point in Time Recovery
Date: 2004-07-13 22:56:31
Message-ID: 19894.1089759391@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers pgsql-patches

Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2004-07-13 23:01:41 Re: Point in Time Recovery
Previous Message Simon Riggs 2004-07-13 22:52:34 Re: Point in Time Recovery

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2004-07-13 22:56:41 Re: [HACKERS] Is "trust" really a good default?
Previous Message Bruce Momjian 2004-07-13 22:56:08 Re: serverlog rotation/functions

Browse pgsql-patches by date

  From Date Subject
Next Message Robert Treat 2004-07-13 22:56:41 Re: [HACKERS] Is "trust" really a good default?
Previous Message Bruce Momjian 2004-07-13 22:56:08 Re: serverlog rotation/functions