Re: Unable to start replica after failover

From: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
To: "Lahnov, Igor" <Igor(dot)Lahnov(at)nexign(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 05:25:41
Message-ID: CAFh8B=n6X6mEtiGBqA=ziQ-=QBUi0OV0=XzZZHV+s0pn3pho9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

On Tue, 23 Aug 2022 at 16:31, Lahnov, Igor <Igor(dot)Lahnov(at)nexign(dot)com> wrote:

>
> Our 'restore_command' on *previous leader* restores a partial file from
> archive (from *new leader*)
>
> ->
> 2022-05-23 01:50:14 [123730]: [1-1]: INFO: pg_probackup archive-get WAL
> file: 000000020000054E000000FB, remote: ssh, threads: 1/1, batch: 1
> <-
>
>
Does it really restore the *partial* file? And why would it do that? The
old primary didn't have a chance to archive 000000020000054E000000FB, the
new primary archived it as 000000020000054E000000FB.partial after promotion.
Postgres is requesting the 000000020000054E000000FB file, but somehow gets
a 000000020000054E000000FB.partial instead. Why?
IMO, pg_probackup does something weird.

Regards,
--
Alexander Kukushkin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter J. Holzer 2022-08-24 06:42:00 Re: Setting up a server with previous day data
Previous Message Kyotaro Horiguchi 2022-08-24 05:18:11 Re: recovery_command has precedence over phisical slots?