Re: SIGFPE handler is naive

On Tue, Aug 14, 2012 at 8:55 AM, ktm(at)rice(dot)edu <ktm(at)rice(dot)edu> wrote:
> On Mon, Aug 13, 2012 at 11:52:06PM -0400, Tom Lane wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> > On Mon, Aug 13, 2012 at 10:14 PM, Noah Misch <noah(at)leadboat(dot)com> wrote:
>> >> Overall, though, I think it best to plug this. We could set a flag before
>> >> each operation, like evaluation of SQL arithmetic, for which SIGFPE is normal.
>>
>> > Yeah, that's what I thought of, too. It seems like it'd be a lot of
>> > work to get there, though.
>>
>> That would depend on how many places there are where SIGFPE is expected.
>> Are we sure there are any? Maybe we should just remove the handler and
>> let SIGFPE be treated as a core dump.
>
> Wouldn't any user level divide-by-zero code cause a SIGFPE?

If it's written in C, sure. If it's written in SQL, no, because we
check for that inside int4div et all.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company