Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM) - Mailing list pgsql-general

From Tom Lane
Subject Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)
Date
Msg-id 10713.1043728937@sss.pgh.pa.us
Whole thread Raw
In response to all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)  (Mark Aufflick <mark@pumptheory.com>)
Responses Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)
Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)
List pgsql-general
Mark Aufflick <mark@pumptheory.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

pgsql-general by date:

Previous
From: Mark Aufflick
Date:
Subject: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)
Next
From: Andrey Mosienko
Date:
Subject: A powerful dump utility