| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Alvaro Herrera" <alvherre(at)dcc(dot)uchile(dot)cl>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | <mascarm(at)mascari(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Point in Time Recovery |
| Date: | 2004-07-13 12:18:11 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA40184D145@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The starting a new timeline thought works for xlogs, but not for clogs.
> No matter how far you go into the future, there is a small (yet
> vanishing) possibility that there is a yet undiscovered committed
> transaction in the future. (Because transactions are ordered in the clog
> because xids are assigned sequentially at txn start, but not ordered in
> the xlog where they are recorded in the order the txns complete).
Won't ExtendCLOG take care of this with ZeroCLOGPage ? Else the same problem
would arise at xid wraparound, no ?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-07-13 12:47:12 | Re: Point in Time Recovery |
| Previous Message | Simon Riggs | 2004-07-13 11:38:23 | Re: Point in Time Recovery |