On 08/04/2011 09:07 AM, Hannu Krosing wrote:
> I have been helping some people to debug a SIGALARM related crash
> induced by using pl/perlu http get functionality
> I have been so far able to repeat the crash only on Debian 64 bit
> computers. DB create script and instructions for reproducing the crash
> The crash is related to something leaving begind a bad SIGALARM handler,
> as it can be (kind of) fixed by resetting sigalarm to nothing using perl
So doesn't this look like a bug in the perl module that sets the signal
handler and doesn't restore it?
What happens if you wrap the calls to the module like this?:
# do LWP stuff here
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.
In response to
pgsql-hackers by date
|Next:||From: Hannu Krosing||Date: 2011-08-04 13:47:03|
|Subject: Re: plperl crash with Debian 6 (64 bit), pl/perlu,
libwww and https|
|Previous:||From: Kevin Grittner||Date: 2011-08-04 13:40:28|
|Subject: Re: Compressing the AFTER TRIGGER queue|