Re: sync_standbys_defined read/write race on startup

Kirill Reshke <reshkekirill@gmail.com>

From: Kirill Reshke <reshkekirill@gmail.com>

To: "Maksim.Melnikov" <m.melnikov@postgrespro.ru>

Cc: pgsql-hackers@lists.postgresql.org

Date: 2025-03-26T19:48:54Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix race with synchronous_standby_names at startup
- e2f42f812a80 13.21 landed
- 873aff945a7b 14.18 landed
- ec59500a1740 15.13 landed
- c922ae2c42a6 16.9 landed
- 3339847ccde0 17.5 landed
- 2e57790836c6 18.0 landed

On Wed, 26 Mar 2025 at 21:18, Maksim.Melnikov <m.melnikov@postgrespro.ru> wrote:
>

> So my question is
> can we accept such behavior as bug of postgres codebase, or, on other way, it is bug of unstable test?
> P.S.
> For me it is looking strange, that postgres start processing workload before full config initializing.
> Attached possible patch for codebase.
>
> Best regards
> Melnikov Maksim

We do not tolerate TAP test flaps. Your repro is OK, can we have
deterministic test here using injection point technique?



-- 
Best regards,
Kirill Reshke