Re: pg_rewind is not crash safe - Mailing list pgsql-hackers

From Andrey M. Borodin
Subject Re: pg_rewind is not crash safe
Date
Msg-id 8604C380-E070-4853-A6FA-D20AFA0B918B@yandex-team.ru
Whole thread Raw
In response to pg_rewind is not crash safe  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers

> 5 авг. 2020 г., в 23:13, Heikki Linnakangas <hlinnaka@iki.fi> написал(а):
>
> A colleague of mine brought to my attention that pg_rewind is not crash safe. If it is interrupted for any reason, it
leavesbehind a data directory with a mix of data from the source and target images. If you're "lucky", the server will
startup, but it can be in an inconsistent state.  

FWIW we routinely encounter cases when after unsuccessful pg_rewind databases refuses to start with "contrecord
requested"message. 
I did not investigate this in detail yet, but I think it is a result of wrong redo recptr written to control file (due
tointerruption or insufficient present WAL segments). 

Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: "Andrey M. Borodin"
Date:
Subject: Re: Amcheck: do rightlink verification with lock coupling
Next
From: Noah Misch
Date:
Subject: Re: public schema default ACL