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-09-05 14:06:53 |
Message-ID: | 201209051606.54062.andres@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sunday, August 26, 2012 06:10:02 PM Andres Freund wrote:
> On Saturday, August 25, 2012 06:38:09 AM Tom Lane wrote:
> > Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > > Doing a pqsignal(SIGFPE, FloatExceptionHandler) after PERL_SYS_INIT3
> > > seems to work. Is that acceptable?
> >
> > Surely that's breaking perl's expectations, to more or less the same
> > degree they're breaking ours?
>
> In the referenced bug they agree that this is the way forward.
As nobody has any better ideas here is a patch doing that:
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
0001-Reset-SIGFPE-handler-after-plperl-initialization.patch | text/x-patch | 2.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2012-09-05 14:15:19 | Re: Cascading replication and recovery_target_timeline='latest' |
Previous Message | boy | 2012-09-05 13:57:12 | BUG #7521: Cannot disable WAL log while using pg_dump |