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 11428.1355854874@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_basebackup from cascading standby after timeline switch  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> writes:
> On Tue, Dec 18, 2012 at 8:09 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> What I'm saying is that the new history file is created from the old
>> one, so the latest file includes all the history as a direct copy. The
>> only thing new is one line of information.

> The timeline history file includes only ancestor timelines history. So
> the latest one might not include all the history.

Indeed.  And even if there are a thousand of them, so what?  It'd still
be less space than a single WAL segment file.

Better to keep the data than wish we had it later.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Error restoring from a base backup taken from standby
Next
From: Tom Lane
Date:
Subject: Re: [ADMIN] Problems with enums after pg_upgrade