Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https - Mailing list pgsql-hackers

From Alex Hunsaker
Subject Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https
Date
Msg-id CAFaPBrTzT=nJHZcBMrRfhHiWfY50WGw5Ner5N6Xn0EFtczfWeQ@mail.gmail.com
Whole thread Raw
In response to Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https
List pgsql-hackers
On Thu, Aug 4, 2011 at 16:34, David E. Wheeler <david@kineticode.com> wrote:
> On Aug 4, 2011, at 3:09 PM, Alex Hunsaker wrote:
>
>> Mainly the options im thinking about are:
>> 1) if anyone touches %SIG die
>> 2) turn %SIG into a regular hash so people can set/play with %SIG, but
>> it has no real effect.
>
> These would disable stuff like $SIG{__WARN__} and $SIG{__DIE__}, which would be an unfortunate side-effect.

Yeah,  good point.

>> 3) local %SIG before we call their trigger function. This lets signals
>> still work while "in trigger scope" (like we do for %_TD)
>
> +1

That seems to be what most people up-thread thought as well. I dont
see it being too expensive. Ill see if I can whip something up today.


pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https
Next
From: Tom Lane
Date:
Subject: Re: error: could not find pg_class tuple for index 2662