From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_basebackup from cascading standby after timeline switch |
Date: | 2012-12-18 00:53:31 |
Message-ID: | 14636.1355792011@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On 17 December 2012 14:16, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
>> I also wonder if pg_basebackup should
>> include *all* timeline history files in the backup, not just the latest one
>> strictly required to restore.
> Why? the timeline history file includes the previous timelines already.
The original intention was that the WAL archive might contain multiple
timeline files corresponding to various experimental recovery attempts;
furthermore, such files might be hand-annotated (that's why there's a
comment provision). So they would be at least as valuable from an
archival standpoint as the WAL files proper. I think we ought to just
copy all of them, period. Anything less is penny-wise and
pound-foolish.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-12-18 01:40:10 | Re: trouble with pg_upgrade 9.0 -> 9.1 |
Previous Message | Tom Lane | 2012-12-18 00:47:37 | Re: multiple CREATE FUNCTION AS items for PLs |