Re: Incorrect snapshots while promoting hot standby node when 2PC is used - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Incorrect snapshots while promoting hot standby node when 2PC is used
Date
Msg-id YLTYfUE7VEZvtqeD@paquier.xyz
Whole thread Raw
In response to Re: Incorrect snapshots while promoting hot standby node when 2PC is used  (Andres Freund <andres@anarazel.de>)
Responses Re: Incorrect snapshots while promoting hot standby node when 2PC is used  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Thu, May 27, 2021 at 10:01:49AM -0700, Andres Freund wrote:
> Why would it be intrusive? We're talking a split second here, no? More
> importantly, I don't think it's correct to release the locks at that
> point.

I have been looking at all that for the last couple of days, and
checked the code to make sure that relying on RecoveryInProgress() as
the tipping point is logically correct in terms of virtual XID,
snapshot build and KnownAssignedXids cleanup.  This stuff is tricky
enough that I may have missed something, but my impression (and
testing) is that we should be safe.

I am adding this patch to the next CF for now.  More eyes are needed.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: postgres_fdw: Handle boolean comparison predicates
Next
From: Alexander Pyhalov
Date:
Subject: join pushdown and issue with foreign update