Hi, On 2022-11-04 10:26:38 -0700, Gurjeet Singh wrote: > The attached patch makes the pg_reload_conf() function set > ConfigReloadPending to true, which will force the postgres main > command-processing loop to process and apply config changes _before_ > executing the next command.
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. 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. Greetings, Andres Freund
