public inbox for [email protected]
help / color / mirror / Atom feedFrom: Nathan Bossart <[email protected]>
To: Kirill Reshke <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: add assertion for palloc in signal handlers
Date: Wed, 18 Feb 2026 11:37:14 -0600
Message-ID: <aZX4yo30-WtmEBhD@nathan> (raw)
In-Reply-To: <aZXe47ZFcrOOKXh3@nathan>
References: <aZTqurNQG-cDzJcL@nathan>
<CALdSSPgFNJ7HK93QbAk2K+Vr88dtuG5t7nGaRF7S6rmcmGpTaA@mail.gmail.com>
<aZXe47ZFcrOOKXh3@nathan>
On Wed, Feb 18, 2026 at 09:46:43AM -0600, Nathan Bossart wrote:
> On Wed, Feb 18, 2026 at 12:13:46PM +0500, Kirill Reshke wrote:
>> Hi! I tested patch under --single (single user mode), and ISTM that we
>> can reach palloc from ProcessInterrups here?
>> Maybe we should not elog in single user mode inside sighandler...
>
> This is reproducible even without single-user mode by sending SIGQUIT to a
> client backend. Both die() and quickdie() call ereport(), and both are
> commonly used as signal handlers for SIGTERM and SIGQUIT.
I also just got an assertion failure due to something in the startup
process. Unfortunately I lost it before digging further, but I think it
was the proc_exit() call in StartupProcShutdownHandler(). I'll try to
reproduce it to get more details. In any case, I'm a bit worried that
these assertions will cause quite a bit of noise. I think we'd better
concoct a plan for dealing with them prior to inflicting the buildfarm.
--
nathan
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: add assertion for palloc in signal handlers
In-Reply-To: <aZX4yo30-WtmEBhD@nathan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox