Re: Unable to start replica after failover
| От | Alexander Kukushkin |
|---|---|
| Тема | Re: Unable to start replica after failover |
| Дата | |
| Msg-id | CAFh8B=n6X6mEtiGBqA=ziQ-=QBUi0OV0=XzZZHV+s0pn3pho9Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | RE: Unable to start replica after failover ("Lahnov, Igor" <Igor.Lahnov@nexign.com>) |
| Ответы |
RE: Unable to start replica after failover
|
| Список | pgsql-general |
Hi,
On Tue, 23 Aug 2022 at 16:31, Lahnov, Igor <Igor.Lahnov@nexign.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
В списке pgsql-general по дате отправления: