Skip site navigation (1) Skip section navigation (2)

pgsql: Make archive recovery always start a new timeline, rather than

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Make archive recovery always start a new timeline, rather than
Date: 2007-09-29 01:36:29
Message-ID: 20070929013629.9ABFC753E4C@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Make archive recovery always start a new timeline, rather than only when a
recovery stop time was used.  This avoids a corner-case risk of trying to
overwrite an existing archived copy of the last WAL segment, and seems
simpler and cleaner all around than the original definition.  Per example
from Jon Colverson and subsequent analysis by Simon.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/doc/src/sgml:
        backup.sgml (r2.75.2.2 -> r2.75.2.3)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/backup.sgml?r1=2.75.2.2&r2=2.75.2.3)
    pgsql/src/backend/access/transam:
        xlog.c (r1.222.2.5 -> r1.222.2.6)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.222.2.5&r2=1.222.2.6)

pgsql-committers by date

Next:From: Tom LaneDate: 2007-09-29 01:36:40
Subject: pgsql: Make archive recovery always start a new timeline, rather than
Previous:From: Tom LaneDate: 2007-09-29 01:36:19
Subject: pgsql: Make archive recovery always start a new timeline, rather than

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group