| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mark Aufflick <mark(at)pumptheory(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM) |
| Date: | 2003-01-28 04:42:17 |
| Message-ID: | 10713.1043728937@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gabriel Munteanu | 2003-01-28 04:47:06 | Re: migrating from progress dbms |
| Previous Message | Mark Aufflick | 2003-01-28 04:13:38 | all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM) |