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:40 |
Message-ID: | 20070929013640.07F8E753E4C@cvs.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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_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)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-29 02:18:15 | pgsql: Defend against openssl libraries that fail on keys longer than |
Previous Message | Tom Lane | 2007-09-29 01:36:29 | pgsql: Make archive recovery always start a new timeline, rather than |