Re: BUG #13644: 2xRecovery without new writes, causes archiving failure

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Amir Rohan <amir(dot)rohan(at)mail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13644: 2xRecovery without new writes, causes archiving failure
Date: 2015-09-28 07:14:23
Message-ID: CAB7nPqQJ9YBr96sj-BCp2EPqw9bDT_ax2GaPu1WRM6V9jbqcwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Sep 27, 2015 at 6:03 AM, Amir Rohan wrote:
> On 09/26/2015 02:39 PM, Michael Paquier wrote:
> I can reproduced this 100% of the time with HEAD from the last few days,
> and haven't tried with anything else.
>
> See attached log+shell-script I used to reproduce.
> The log shows the contents of the archive directory at various points
> in the process I described in the initial post.

If there is a bug, that's in your script, not in the backend code.
restore_command should point to ARCHIVE_DIR instead of BACKUP_DIR.
That's the reason why the third node (2nd recovery) cannot switch to
timeline 3: it cannot find the history file of timeline 2 properly.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Amir Rohan 2015-09-28 07:27:15 Re: BUG #13644: 2xRecovery without new writes, causes archiving failure
Previous Message digoal 2015-09-28 06:15:24 BUG #13645: pg_basebackup backup hash index & unlogged table