Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Hannu Krosing <hannu(at)krosing(dot)net>
Cc: 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 14:34:44
Message-ID: 4E3AAE04.5080700@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/04/2011 09:53 AM, Hannu Krosing wrote:
>
>> What happens if you wrap the calls to the module like this?:
>>
>> {
>> local $SIG{ALRM};
>> # do LWP stuff here
>> }
>> return 'OK';
>>
>>
>> That should restore the old handler on exit from the block.
>>
>> I think if you use a perl module that monkeys with the signal handlers
>> for any signal postgres uses all bets are off.
> Sure, but how expensive would it be for pl/perl to do this
> automatically ?
>
>

Probably not very. It could possibly be added to
plc_perlboot.pl::mkfuncsrc() after the prolog, or maybe before.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexey Klyukin 2011-08-04 14:38:11 Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https
Previous Message Tom Lane 2011-08-04 14:28:45 Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https