Re: pg_basebackup from cascading standby after timeline switch

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-17 16:58:11
Message-ID: CABUevEyZzSwAKnHZpqc2Pjo1RC0V-EAv8LYPcuvm1W-kZcrsfA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 17, 2012 at 5:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
>> I'm not happy with the fact that we just ignore the problem in a backup
>> taken from a standby, silently giving the user a backup that won't start
>> up. Why not include the timeline history file in the backup?
>
> +1. I was not aware that we weren't doing that --- it seems pretty
> foolish, especially since as you say they're tiny.

Yeah, +1. That should probably have been a part of the whole
"basebackup from slave" patch, so it can probably be considered a
back-patchable bugfix in itself, no?

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2012-12-17 17:02:51 configure.in and setproctitle/optreset problem
Previous Message Cédric Villemain 2012-12-17 16:49:19 Re: Makefiles don't seem to remember to rebuild everything anymore