Re: recovery is stuck when children are not processing SIGQUIT from previous crash - Mailing list pgsql-admin

From Marko Kreen
Subject Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Date
Msg-id e51f66da0911120419u31598de4y8771df7a8b6bf2ea@mail.gmail.com
Whole thread Raw
In response to Re: recovery is stuck when children are not processing SIGQUIT from previous crash  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-admin
On 11/12/09, Peter Eisentraut <peter_e@gmx.net> wrote:
> On lör, 2009-09-26 at 12:19 -0400, Tom Lane wrote:
>  > Peter Eisentraut <peter_e@gmx.net> writes:
>  > > strace on the backend processes all showed them waiting at
>  > > futex(0x7f1ee5e21c90, FUTEX_WAIT_PRIVATE, 2, NULL
>  > > Notably, the first argument was the same for all of them.
>  >
>  > Probably means they are blocked on semaphores.  Stack traces would
>  > be much more informative ...

>  Looks like a race condition or lockup in the syslog code.

AFAICS syslog() is not safe to use in signal handler:

  http://www.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_04_03_03

--
marko

pgsql-admin by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Next
From: Tom Lane
Date:
Subject: Re: recovery is stuck when children are not processing SIGQUIT from previous crash