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

Поиск
Список
Период
Сортировка
От Vivek Khera
Тема Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)
Дата
Msg-id x78yx5gouv.fsf@onceler.kciLink.com
обсуждение исходный текст
Ответ на Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
>>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.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@kciLink.com       Rockville, MD       +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera   http://www.khera.org/~vivek/

В списке pgsql-general по дате отправления:

Предыдущее
От: Vivek Khera
Дата:
Сообщение: Re: ERROR: No one parent tuple was found
Следующее
От: Vivek Khera
Дата:
Сообщение: Re: Using RSYNC for replication?