RE: Unable to start replica after failover - Mailing list pgsql-general

From Lahnov, Igor
Subject RE: Unable to start replica after failover
Date
Msg-id 18b2bc57e3a3455fa01690cdd0b3efd3@nexign.com
Whole thread Raw
In response to Re: Unable to start replica after failover  (Alexander Kukushkin <cyberdemn@gmail.com>)
List pgsql-general

As far as I understand, according to the logs, the last leader does not yet know about the new timeline

and it is trying to download the full log from the previous timeline.

It seems there should be a conflict that the partial file already exists locally when restoring in this case, but this does not happen.

And the partial file from the new leader loaded as a full log.

What do you think it is possible to add a check to the restore command, that a partial or full file already exists?

Or is disabling the restore command a possible solution in this case?

pgsql-general by date:

Previous
From: Lutz Horn
Date:
Subject: Re: Postgres SQL unable to handle Null values for Text datatype
Next
From: Alexander Kukushkin
Date:
Subject: Re: Unable to start replica after failover