| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: XLog: how to log? |
| Date: | 2004-05-11 21:58:25 |
| Message-ID: | 1084312704.3028.2155.camel@stromboli |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2004-05-11 at 21:29, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > Currently, recovery loops until end of xlogs. There is no exit condition
> > from the loop. There is not currently a timestamp on the xlogs -
> > anywhere apart from the file date on each xlog.
>
> Sure there is: every transaction commit record (and I think abort as
> well) carries a timestamp. This was put in with PITR in mind in the
> very beginning.
>
When being wrong has a purpose, I just love it.
I'll put my code-goggles back on the right way round.
Thanks, Simon
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-05-11 21:59:28 | Re: PITR Signalling the Archiver |
| Previous Message | Tom Lane | 2004-05-11 21:53:32 | Re: XLog: how to log? |