| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PITR Phase 2 - Design Planning |
| Date: | 2004-04-26 23:32:17 |
| Message-ID: | 200404262332.i3QNWHH04768@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> On Mon, 2004-04-26 at 23:01, Alvaro Herrera wrote:
> > On Mon, Apr 26, 2004 at 05:05:41PM -0400, Bruce Momjian wrote:
> > > Simon Riggs wrote:
> > > > Transaction log files currently have timestamps, so that is
> > > > straightforward, but probably not the best we can do. We would
> > > > rollforward until the xlog file time > desired point in time.
> > >
> > > I was thinking --- how would someone know the time to use for restore?
> >
> > I think there should be a way to get a TransactionId and restore up to
> > that point. It'd be cool, but not required, if the system showed what
> > valid TransactionIds there are, and roughly what they did (the xlog
> > code already has "describers" everywhere AFAICS).
>
> You're right, I think we should start by implementing the rollforward to
> a txnid before we consider the rollforward to a specified point-in-time.
> All the hooks for that are already there...
Yep, sounds like a plan.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-04-26 23:46:46 | Re: PITR Phase 1 - Test results |
| Previous Message | Simon Riggs | 2004-04-26 22:20:01 | Re: PITR Phase 2 - Design Planning |