Re: Refactor pg_rewind code and make it work against a standby - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Refactor pg_rewind code and make it work against a standby
Date
Msg-id 20201120171420.zqhqbp4ytu6fblre@alap3.anarazel.de
Whole thread Raw
In response to Re: Refactor pg_rewind code and make it work against a standby  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Refactor pg_rewind code and make it work against a standby  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
Hi,

On 2020-11-20 16:19:03 +0200, Heikki Linnakangas wrote:
> Pushed a fix similar to your patch, but I put the wait_for_catchup() before
> running pg_rewind. The point of inserting the 'in A, after C was promoted'
> row is that it's present in B when pg_rewind runs.

Hm - don't we possibly need *both*? Since post pg_rewind recovery starts
at the previous checkpoint, it's quite possible for C to get ready to
answer queries before that record has been replayed?

Thanks,

Andres Freund



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: enable_incremental_sort changes query behavior
Next
From: "David G. Johnston"
Date:
Subject: Re: abstract Unix-domain sockets