Re: Fix 035_standby_logical_decoding.pl race conditions
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, 'Amit Kapila' <amit.kapila16@gmail.com>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2025-04-08T06:27:41Z
Lists: pgsql-hackers
On Tue, Apr 08, 2025 at 06:19:02AM +0000, Bertrand Drouvot wrote: > - A new injection_points_wakeup_detach() function that is holding the spinlock > during the whole duration to ensure that no process can wait in between the > wakeup and the detach. That would not a correct spinlock use. injection_points_detach() and injection_points_wakeup_internal() do much more actions than what we can internally do while holding a spinlock, including both Postgres-specific calls as well as system calls. strcmp() and strlcpy() are still OK-ish, even as system calls, as they work directly on the strings given in input. -- Michael
Commits
-
Stabilize 035_standby_logical_decoding.pl.
- 105b2cb33617 18.0 landed
- 17a165d60f73 17.5 landed
- 86392e8827d8 16.9 landed