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

From spock@mgnet.de
Subject Re: Point in Time Recovery
Date
Msg-id Pine.LNX.4.58.0407080852370.18718@spock.intra.net
Whole thread Raw
In response to Re: Point in Time Recovery  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
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?"

Just my 2ct :-))

Greetings, Klaus

-- 
Full Name   : Klaus Naumann     | (http://www.mgnet.de/) (Germany)
Phone / FAX : ++49/177/7862964  | E-Mail: (kn@mgnet.de)


pgsql-hackers by date:

Previous
From: Mike Rylander
Date:
Subject: Re: Nested Transactions, Abort All
Next
From: Pierre Emmanuel Gros
Date:
Subject: storage manager