| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Alex Hunsaker <badalex(at)gmail(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:34:32 |
| Message-ID: | 415279B0-C0A8-4D63-94F2-094A18482C56@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
> 3) local %SIG before we call their trigger function. This lets signals
> still work while "in trigger scope" (like we do for %_TD)
+1
> 4) if we can't get any of the above to work we can save each %SIG
> handler before and restore them after each trigger call. (mod_perl
> does something similar so Im fairly certain we should be able to get
> that to work)
+1
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Hunsaker | 2011-08-04 22:46:21 | Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https |
| Previous Message | Jeff Davis | 2011-08-04 22:28:04 | Re: Transient plans versus the SPI API |