Re: [BUG] Archive recovery failure on 9.3+.

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, Josh Berkus <josh(at)agliodbs(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [BUG] Archive recovery failure on 9.3+.
Date: 2014-02-13 14:01:16
Message-ID: 52FCD02C.3060201@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/13/2014 03:53 PM, Christoph Berg wrote:
> Is removing the "test ! -f" part and hence overwriting files in the
> archive safe, i.e. are the files the same?

No. Not in general, anyway. If the old master keeps running, even for a
moment, after the partial file was copied, it will have created more WAL
records which are present in the old master's copy of the segment, but
not in the standby's.

You could perhaps use "diff" as part of archive_command, to check if
archived version is identical to the one about to be archived.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2014-02-13 14:02:24 Re: Weaker shmem interlock w/o postmaster.pid
Previous Message Christoph Berg 2014-02-13 13:53:41 Re: [BUG] Archive recovery failure on 9.3+.