[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-committers
Subject:    [COMMITTERS] pgsql: Make archive recovery always start a new timeline, rather than
From:       tgl () postgresql ! org (Tom Lane)
Date:       2007-09-29 1:36:40
Message-ID: 20070929013640.07F8E753E4C () cvs ! postgresql ! org
[Download RAW message or body]

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_0_STABLE

Modified Files:
--------------
    pgsql/doc/src/sgml:
        backup.sgml (r2.54.4.6 -> r2.54.4.7)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/backup.sgml?r1=2.54.4.6&r2=2.54.4.7)
  pgsql/src/backend/access/transam:
        xlog.c (r1.180.4.5 -> r1.180.4.6)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.180.4.5&r2=1.180.4.6)


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org


[prev in list] [next in list] [prev in thread] [next in thread]