| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SIGFPE handling |
| Date: | 2026-11-12 15:17:33 |
| Message-ID: | 3830012.1794496653@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> So, I propose to:
> 1. Change FloatExceptionHandler() to PANIC instead of ERROR
> 2. Install FloatExceptionHandler() in all processes.
Agree on #2, violently against #1. Why is it an improvement for
division-by-zero to take down the entire system?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2026-11-12 15:18:08 | Re: reconsider_full_join_clause fails to consider if COALESCE() arguments are NULL-preserving |
| Previous Message | Álvaro Herrera | 2026-11-12 14:35:25 | Re: ATTACH PARTITION cost grows linearly with pg_constraint size (seqscan in CloneFkReferenced), much worse since not-null constraints are in pg_constraint (PG 18) |