| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 14:58:18 |
| Message-ID: | 201208241658.18791.andres@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday, August 24, 2012 04:53:36 PM Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)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?
Greetings,
Andres
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-08-24 15:03:16 | Re: pg_upgrade's exec_prog() coding improvement |
| Previous Message | Tom Lane | 2012-08-24 14:53:36 | Re: plperl sigfpe reset can crash the server |