Andres Freund <and...@2ndquadrant.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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
