Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)

Ahhh,

yes, um, (looks to see if anyone noticed) that would be the:

use sigtrap qw(die untrapped normal-signals stack-trace any
error-signals);

line in my code...

i will get rid of the 'untrapped normal-signals' and report back.

ta.

On Tuesday, January 28, 2003, at 03:42 PM, Tom Lane wrote:

> Mark Aufflick <mark(at)pumptheory(dot)com> writes:
>> DEBUG: server process (pid 971) was terminated by signal 14
>
> Hm, that's SIGALRM on my box, I assume so on yours too.
>
> AFAICT, there is no part of the Postgres code that runs with SIGALRM
> set to default handling: it's either SIG_IGN or the deadlock timer
> handler.
>
>> Both plpgsql and plperlu are used (plperlu is used for one trigger
>> function to post a single https form that sends an sms message, and
>> record the result body).
>
> I wonder whether the Perl interpreter is hacking on the SIGALRM
> setting. That would be pretty unfriendly of it (but I don't think
> Perl quite believes the notion that it might be only a subroutine
> library, and not in full control of the process...)
>
> regards, tom lane