| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Alex Hunsaker <badalex(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
| Subject: | Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https |
| Date: | 2011-08-09 16:22:46 |
| Message-ID: | 28045.1312906966@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 08/08/2011 05:03 AM, Tim Bunce wrote:
>> After giving it some more thought it seems reasonable to simply force the
>> SIGALRM handler back to postgres when a plperlu function returns:
>> pqsignal(SIGALRM, handle_sig_alarm);
> Maybe we need to do this in some more centralized spot. It seems
> unlikely that this problem is unique to plperlu, or even just confined
> to PLs.
No. As I pointed out upthread, the instant somebody changes the SIGALRM
handler to a non-Postgres-aware one, you are already at risk of failure.
Setting it back later is just locking the barn door after the horses
left. Institutionalizing such a non-fix globally is even worse.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-08-09 16:35:35 | Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https |
| Previous Message | Tom Lane | 2011-08-09 16:16:16 | Re: Compiler warnings with stringRelOpts (was WIP: Fast GiST index build) |