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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: 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 15:43:06
Message-ID: 4E41558A.9070905@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-08-09 16:07:14 Re: Enforcing that all WAL has been replayed after restoring from backup
Previous Message Heikki Linnakangas 2011-08-09 15:25:27 Re: Compiler warnings with stringRelOpts (was WIP: Fast GiST index build)