Re: Point in Time Recovery - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Point in Time Recovery
Date
Msg-id 1089722832.17493.2534.camel@stromboli
Whole thread Raw
In response to Re: Point in Time Recovery  ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>)
List 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



pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: Point in Time Recovery
Next
From: Bruce Momjian
Date:
Subject: Re: possibly updating techdocs; mysql2pgsql on gborg