| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Hannu Krosing <hannu(at)2ndquadrant(dot)com> |
| Subject: | Re: plperl sigfpe reset can crash the server |
| Date: | 2012-08-24 05:33:01 |
| Message-ID: | 10902.1345786381@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>> Um ... how exactly can that happen, if the signal is now ignored?
> My man 2 signal tells me:
> "According to POSIX, the behavior of a process is undefined after it ignores
> a SIGFPE, SIGILL, or SIGSEGV signal that was not generated by kill(2) or
> raise(3)."
So I guess the real question there is: WTF is perl doing setting the
handling to SIG_IGN?
Even if you grant the proposition that perl knows what it's doing in
terms of its internal behavior, which given the above seems doubtful,
it has no business overriding a host application's signal settings
like that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-08-24 05:45:59 | Re: plperl sigfpe reset can crash the server |
| Previous Message | Andres Freund | 2012-08-24 05:32:49 | Re: plperl sigfpe reset can crash the server |