RE: Unable to start replica after failover

From: "Lahnov, Igor" <Igor(dot)Lahnov(at)nexign(dot)com>
To: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, "Timonin, Alexey" <Alexey(dot)Timonin(at)nexign(dot)com>, "Dmitriyev, Andrey" <Andrey(dot)Dmitriyev(at)nexign(dot)com>, "Vassiliev, Andrey" <Andrey(dot)Vassiliev(at)nexign(dot)com>
Subject: RE: Unable to start replica after failover
Date: 2022-08-24 11:37:09
Message-ID: 27cb3d242a9d4b88a6f1e22ba9716441@nexign.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,
Yes, the *patial* from the *new leader* is restored to *last leader* and renamed to 000000020000054E000000FB, without *partial* postfix.

>>Postgres asks for file 000000020000054E000000FB but somehow gets
>>000000020000054E000000FB.partial instead. Why?

Yes, Postgres asks for 000000020000054E000000FB and gets renamed 000000020000054E000000FB.partial (without *partial* postfix).

And, finally, the *last leader* has a local 000000020000054E000000FB.partial, with the segments needed for recovery, and 000000020000054E000000FB ( renamed 000000020000054E000000FB.partial from new leader). But 000000020000054E000000FB has a higher priority than 000000020000054E000000FB.partial
Also, the *new leader* archives full 000000030000054E000000FB of the new timeline. And this file contains the same as 000000020000054E000000FB data.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2022-08-24 13:51:55 Re: Setting up a server with previous day data
Previous Message Laurenz Albe 2022-08-24 11:00:10 Re: recovery_command has precedence over phisical slots?