Re: how to switch old replication Master to new Standby after promoting old Standby - pg_rewind log file missing

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: John Lumby <johnlumby(at)hotmail(dot)com>
Cc: pgsql general <pgsql-general(at)postgresql(dot)org>, "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>, "adrian(dot)klaver(at)aklaver(dot)com" <adrian(dot)klaver(at)aklaver(dot)com>
Subject: Re: how to switch old replication Master to new Standby after promoting old Standby - pg_rewind log file missing
Date: 2016-03-15 16:21:50
Message-ID: CAB7nPqQgBjJXk_Zu16PDc9iQpGqnakScE+-TP8-eEFYiru=NTA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Mar 15, 2016 at 5:14 PM, John Lumby <johnlumby(at)hotmail(dot)com> wrote:
> But my question is, given that the divergence point was 2B000060,
> why is it looking for a file earlier than that?

(please do not top-post, this is annoying as it breaks the logic of the thread)
pg_rewind begins scanning WAL records not at the point where WAL
forked, but from the previous checkpoint record before WAL forked.
--
Michael

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message otheus uibk 2016-03-15 17:26:49 How to Qualifying or quantify risk of loss in asynchronous replication
Previous Message Michael Paquier 2016-03-15 16:18:49 Re: pg_dump crashing