On Friday, August 24, 2012 05:09:18 PM Andrew Dunstan wrote: > On 08/24/2012 10:58 AM, Andres Freund wrote: > > On Friday, August 24, 2012 04:53:36 PM Tom Lane wrote: > >> Andres Freund <and...@2ndquadrant.com> writes: > >>> ./pod/perl581delta.pod: > >>> At startup Perl blocks the SIGFPE signal away since there isn't much > >>> Perl can do about it. Previously this blocking was in effect also for > >>> programs executed from within Perl. Now Perl restores the original > >>> SIGFPE handling routine, whatever it was, before running external > >>> programs. > >> > >> So there's a gap in the "restore" logic someplace. > > > > Well, the logic is not triggering at all in pg's case. Its just used if > > perl is exec()ing something... > > > >>> perl.h also has some tidbits: ... > >>> That doesn't sound very well reasoned and especially not very well > >>> tested to me. > >> > >> Time to file a Perl bug? > > > > Anybody more involved in the perl community volunteering? > > Just run perlbug and let us know the bug number. https://rt.perl.org/rt3/Public/Bug/Display.html?id=114574
Andres -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
