Re: pg_basebackup from cascading standby after timeline switch - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_basebackup from cascading standby after timeline switch
Date
Msg-id 14636.1355792011@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_basebackup from cascading standby after timeline switch  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: pg_basebackup from cascading standby after timeline switch  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On 17 December 2012 14:16, Heikki Linnakangas <hlinnakangas@vmware.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: multiple CREATE FUNCTION AS items for PLs
Next
From: Bruce Momjian
Date:
Subject: Re: [ADMIN] Problems with enums after pg_upgrade