| 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:11 |
| Message-ID: | 20070929013611.44625753E4C@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.
Modified Files:
--------------
pgsql/doc/src/sgml:
backup.sgml (r2.102 -> r2.103)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/backup.sgml?r1=2.102&r2=2.103)
pgsql/src/backend/access/transam:
xlog.c (r1.282 -> r1.283)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.282&r2=1.283)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-29 01:36:19 | pgsql: Make archive recovery always start a new timeline, rather than |
| Previous Message | Tom Lane | 2007-09-29 00:14:40 | pgsql: Make use of additional chklocale.c entries to reject locales that |