| From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SIGFPE handler is naive |
| Date: | 2012-08-14 12:55:02 |
| Message-ID: | 20120814125502.GN27500@aart.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
>
> regards, tom lane
>
Wouldn't any user level divide-by-zero code cause a SIGFPE?
Regards,
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-08-14 12:56:43 | Re: default_isolation_level='serializable' crashes on Windows |
| Previous Message | Robert Haas | 2012-08-14 12:40:06 | Re: SIGFPE handler is naive |