Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-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

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-09-26 16:28:15
Subject: Re: Join optimization for inheritance tables
Previous:From: Simon RiggsDate: 2009-09-26 16:19:13
Subject: Re: Join optimization for inheritance tables

pgsql-admin by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group