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

From Simon Riggs
Subject Re: Point in Time Recovery
Date
Msg-id 1089283370.17493.348.camel@stromboli
Whole thread Raw
In response to Re: Point in Time Recovery  ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>)
List pgsql-hackers
On Thu, 2004-07-08 at 07:57, spock@mgnet.de wrote:
> On Thu, 8 Jul 2004, Simon Riggs wrote:
> 
> > We don't need to mention timelines in the docs, nor do we need to alter
> > pg_controldata to display it...just a comment in the code to explain why
> > we add a large number to the LogId after each recovery completes.
> 
> I'd disagree on that. Knowing what exactly happens when recovering the
> database is a must. It makes people feel more safe about the process. This
> is because the software doesn't do things you wouldn't expect.
> 
> On Oracle e.g. you create a new database incarnation when you recover a
> database (incomplete). Which means your System Change Number and your Log
> Sequence is reset to 0.
> Knowing this is crucial because you otherwise would wonder "Why is it
> doing that? Is this a bug or a feature?"
> 

OK, will do.

Best regards, Simon Riggs



pgsql-hackers by date:

Previous
From: Karel Zak
Date:
Subject: windows encodings
Next
From: Andrew Piskorski
Date:
Subject: SAN, clustering, MPI, Backplane Re: Postgresql on SAN