| 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-09-06 06:46:38 |
| Message-ID: | 18b2bc57e3a3455fa01690cdd0b3efd3@nexign.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Kukushkin | 2022-09-06 07:16:03 | Re: Unable to start replica after failover |
| Previous Message | Lutz Horn | 2022-09-06 06:25:29 | Re: Postgres SQL unable to handle Null values for Text datatype |