| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PITR Phase 2 - Design Planning |
| Date: | 2004-04-27 22:11:29 |
| Message-ID: | 1083103889.30065.110.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-04-27 22:35:40 | Re: PITR Phase 2 - Design Planning |
| Previous Message | Simon Riggs | 2004-04-27 21:36:29 | Re: PITR Phase 2 - Design Planning |