Re: pg_reload_conf() synchronously - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_reload_conf() synchronously
Date
Msg-id 2527794.1667619321@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_reload_conf() synchronously  (Andres Freund <andres@anarazel.de>)
Responses Re: pg_reload_conf() synchronously
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> Worth noting that this doesn't necessarily suffice to avoid race conditions in
> tests, if the test depends on *other* backends having seen the configuration
> changes.

True, but do we have any such cases?

> It might be worth to use the global barrier mechanism to count which backends
> have reloaded configuration and to provide a function / option to pg_sleep
> that waits for that.

That ... seems like a lot of mechanism.  And it could easily result
in undetected deadlocks, if any other session is blocked on you.
I seriously doubt that we should go there.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Incorrect include file order in guc-file.l
Next
From: Andres Freund
Date:
Subject: Re: pg_reload_conf() synchronously