Re: Fix 035_standby_logical_decoding.pl race conditions - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Fix 035_standby_logical_decoding.pl race conditions
Date
Msg-id CAA4eK1+x5-eOn5+MW6FiUjB_1bBCH8jCCARC1uMrx6erZ3J73w@mail.gmail.com
Whole thread Raw
In response to RE: Fix 035_standby_logical_decoding.pl race conditions  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
Responses RE: Fix 035_standby_logical_decoding.pl race conditions
List pgsql-hackers
On Tue, Apr 1, 2025 at 6:53 AM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>

With respect to 0001, can't this problem happen for the following case as well?
# Recovery conflict: Invalidate conflicting slots, including in-use slots
# Scenario 5: conflict due to on-access pruning.

You have not added any injection point for the above case. Isn't it
possible that if running_xact record is logged concurrently to the
pruning record, it should move the active slot on standby, and the
same failure should occur in this case as well?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Fix 035_standby_logical_decoding.pl race conditions
Next
From: David Geier
Date:
Subject: Hashed IN only applied to first encountered IN