Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Jurij Grigorev <ju(dot)grigorev(at)ftdata(dot)ru>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace
Date: 2026-09-30 18:20:57
Message-ID: CAOYmi+=fy2Ou-VLJipsngUspODnyqNOpb9hvYmmdyGRF-6spJA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Sep 30, 2026 at 11:00 AM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> The test addition coined with bca67e5a3 is not very robust,
> unfortunately. Buildfarm animal serinus found a way to break it [1]
> as below:

Bleh. These SIGHUP/log file races are really annoying, and I'm going
to need to trawl the list to see if anyone's proposed a more general
solution. (I keep thinking about assigning an xid as a generation
number to an in-memory configuration...)

For now, is the following test giving us much, or can we remove it?
We've already done the wait_for_log(). If that "sequence point" turns
out to be inadequate for some other reason, we'd have to fix it
anyway.

> is($bgconn->query_safe('SHOW oauth_validator_libraries'),
> 'validator', 'oauth_validator_libraries restored');

Thanks,
--Jacob

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Gustafsson 2026-09-30 18:24:56 Re: autovacuum: automatically propagate updated parameters
Previous Message Alexander Lakhin 2026-09-30 18:00:00 Re: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace