Re: PITR Phase 2 - Design Planning - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: PITR Phase 2 - Design Planning
Date
Msg-id 1083103889.30065.110.camel@jester
Whole thread Raw
In response to Re: PITR Phase 2 - Design Planning  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: PITR Phase 2 - Design Planning  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Tue, 2004-04-27 at 17:36, Simon Riggs wrote:
> On Tue, 2004-04-27 at 21:56, Rod Taylor wrote:
> > > Overall, I'd refer back to the points Bruce raised - you certainly do
> > > need a way of finding out the time to recover to, and as others have
> > > said also, time isn't the only desirable "recovery point".
> > 
> > Wouldn't it be sufficient to simply use the transaction ID and ensure
> > that all the parameters the user might want to use to find that ID can
> > be made available in the log files?

> Yes, of course, all methods of locating a particular xlog file to stop
> at are effectively equivalent. The discussion is mostly about what is
> convenient for the user in a real recovery situation.

I see.. The first thing I would need to do is look at /var/log/pgsql. At
that point it really doesn't matter what the identifier is so long as
the identifier is there.



pgsql-hackers by date:

Previous
From: Peter Galbavy
Date:
Subject: Re: PITR Phase 2 - Design Planning
Next
From: Simon Riggs
Date:
Subject: Re: PITR Phase 2 - Design Planning