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

From: Vivek Khera <khera(at)kcilink(dot)com>
To: 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 17:34:32
Message-ID: x78yx5gouv.fsf@onceler.kciLink.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "TL" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

>> DEBUG: server process (pid 20704) was terminated by signal 14

TL> whenever the backend process would next have reached a lock timeout.

TL> I have not dug through the Perl sources to look for mucking with
TL> SIGALRM, but I bet that's what the problem is.

From what I recall, perl takes charge of all signals in order to
deliver them at safe points to your perl program. This is both good
and bad. mod_perl has to deal with perl taking signals from apache.
Perhaps that code could be worth a read.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera(at)kciLink(dot)com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vivek Khera 2003-01-28 17:39:25 Re: Using RSYNC for replication?
Previous Message Vivek Khera 2003-01-28 17:31:15 Re: ERROR: No one parent tuple was found