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

From Bruce Momjian
Subject Re: PITR Phase 2 - Design Planning
Date
Msg-id 200404280400.i3S40AV17520@candle.pha.pa.us
Whole thread Raw
In response to Re: PITR Phase 2 - Design Planning  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: PITR Phase 2 - Design Planning
List pgsql-hackers
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.
> 
> >From all that has been said so far, I would implement:
> 
> 1. Recovery to a specific txnid, which is fairly straightforward
> 2. Recovery to a specific date/time 
> a) either by implementing a log inspection tool that shows the txnid for
> a PIT
> b) implementing recovery to a PIT directly
> 3. Recovery to a named checkpoint

What if we added transaction id to log_line_prefix?  The user could then
log all queries and find the xid where they want to stop, but of course
that assumes they have enabled such logging, and they have access to the
logs.

--  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: [pgsql-advocacy] What can we learn from MySQL?
Next
From: Tom Lane
Date:
Subject: Re: btbulkdelete