Re: recovery is stuck when children are not processing SIGQUIT from previous crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Date: 2009-09-26 16:19:47
Message-ID: 22209.1253981987@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)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 ...

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2009-09-26 16:30:59 Re: postgresql ldap integration
Previous Message Alvaro Herrera 2009-09-25 16:27:58 Re: recovery is stuck when children are not processing SIGQUIT from previous crash

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-09-26 16:28:15 Re: Join optimization for inheritance tables
Previous Message Simon Riggs 2009-09-26 16:19:13 Re: Join optimization for inheritance tables