| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PITR Phase 2 - Design Planning |
| Date: | 2004-04-26 22:20:01 |
| Message-ID: | 1083018000.3018.244.camel@stromboli |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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...
Best regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-04-26 23:32:17 | Re: PITR Phase 2 - Design Planning |
| Previous Message | Simon Riggs | 2004-04-26 22:16:01 | Re: PITR Phase 2 - Design Planning |