| From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)krosing(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https |
| Date: | 2011-08-04 22:46:21 |
| Message-ID: | CAFaPBrTzT=nJHZcBMrRfhHiWfY50WGw5Ner5N6Xn0EFtczfWeQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 4, 2011 at 16:34, David E. Wheeler <david(at)kineticode(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-08-04 23:38:28 | Re: error: could not find pg_class tuple for index 2662 |
| Previous Message | David E. Wheeler | 2011-08-04 22:34:32 | Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https |