| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at> |
| Cc: | 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>, mascarm(at)mascari(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Point in Time Recovery |
| Date: | 2004-07-13 12:47:12 |
| Message-ID: | 1089722832.17493.2534.camel@stromboli |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2004-07-13 at 13:18, Zeugswetter Andreas SB SD wrote:
> > 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 ?
>
Sounds like a good start...
When PITR ends, we need to stop mid-way through a file. Does that handle
that situation?
Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-07-13 13:06:43 | Re: possibly updating techdocs; mysql2pgsql on gborg |
| Previous Message | Zeugswetter Andreas SB SD | 2004-07-13 12:18:11 | Re: Point in Time Recovery |