Re: Do we want to solve reload/config races more generally? (was: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace) - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: Do we want to solve reload/config races more generally? (was: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace)
Date
Msg-id 31E8FD07-F7EF-414D-8C40-A3203BFF0777@yandex-team.ru
Whole thread
In response to Do we want to solve reload/config races more generally? (was: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace)  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: Do we want to solve reload/config races more generally? (was: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace)
List pgsql-hackers

> On 8 Oct 2026, at 23:28, Jacob Champion <jacob.champion@enterprisedb.com> wrote:
>
> The general issue, for anyone new to the problem, is that reloading
> doesn't wait for the effects of the SIGHUP to complete. (And the
> meaning of "complete" depends on the test case.) It feels like this
> would pop up in more situations, but the buildfarm doesn't always show
> it and it's an easy trap to fall into.

Few days ago maintainers of pgconsul (HA tool) asked me: how to wait until
synchronous_stanby_names takes effect? For some reason they need to commit one
transaction with full quorum. The best solution we found was to restart the node
and insert\commit afterwards.

So yeah, +1 for having synchronous reload.


Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Fix a wal_debug crash with the new shmem allocation API
Next
From: Alexander Lakhin
Date:
Subject: Re: 041_checkpoint_at_promote.pl might fail due to race condition on child kill