From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: Julien Rouhaud <rjuju123@gmail.com>, Mats Kindahl <mats@timescale.com>,
        pgsql-bugs@lists.postgresql.org
Subject: Re: Use of signal-unsafe functions from signal handlers
In-reply-to: <Yo18KyPNP0G03n10@paquier.xyz>
References: 
 <CA+14425wJh3m2XA4c8-stRKGQYLwKqFiScqZm7BBt1JxU2iU-g@mail.gmail.com>
 <20220524101418.7pp65powa362vzln@jrouhaud>
 <CA+14426Zpdi6=jr9Z+C_tzS36pVa_+BbCHSeriqd=sLw4X6_iw@mail.gmail.com>
 <20220524123739.6glyxyx4owqpqjnr@jrouhaud> <1531973.1653401755@sss.pgh.pa.us>
 <Yo18KyPNP0G03n10@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
	message dated "Wed, 25 May 2022 09:45:31 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1773722.1653441914.1@sss.pgh.pa.us>
Date: Tue, 24 May 2022 21:25:14 -0400
Message-ID: <1773723.1653441914@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1773723.1653441914%40sss.pgh.pa.us>
Precedence: bulk

Michael Paquier <michael@paquier.xyz> writes:
> Hmm.  Shouldn't we worry about FloatExceptionHandler() that gets used
> on SIGFPE?

SIGFPE is generated synchronously, so that one's not really a problem,
I think: it can only interrupt code that is doing trap-prone arithmetic.
Anyway that code's been like that for ages and nobody has reported an
issue there.

			regards, tom lane