Re: Use of signal-unsafe functions from signal handlers - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: Use of signal-unsafe functions from signal handlers
Date
Msg-id Yo18KyPNP0G03n10@paquier.xyz
Whole thread Raw
In response to Re: Use of signal-unsafe functions from signal handlers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, May 24, 2022 at 10:15:55AM -0400, Tom Lane wrote:
> ereport() itself is just the tip of the iceberg; even if it's safe
> (which I concur it isn't), there's also the atexit/on_proc_exit
> functions that are likely to be called during shutdown.  So yeah,
> this coding is not too safe.  I'm not sure that getting rid of it
> would be a net win though, as we'd replace it-might-crash hazards
> with it-might-never-exit hazards, from bgworkers that neglect to
> respond to ShutdownRequestPending.

Hmm.  Shouldn't we worry about FloatExceptionHandler() that gets used
on SIGFPE?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #17492: error MSB4126: The specified solution configuration "Release|arm64" is invalid
Next
From: Michael Paquier
Date:
Subject: Re: BUG #17495: Regression in 15beta1 when filtering subquery including row_number window function