Re: Fix 035_standby_logical_decoding.pl race conditions
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2025-04-01T11:44:21Z
Lists: 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.
Commits
-
Stabilize 035_standby_logical_decoding.pl.
- 105b2cb33617 18.0 landed
- 17a165d60f73 17.5 landed
- 86392e8827d8 16.9 landed