[moved to -hackers] On tor, 2009-11-12 at 09:35 -0500, Tom Lane wrote: > Peter Eisentraut <pete...@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. > > > Looks like a race condition or lockup in the syslog code. > > Hm, why are there two <signal handler> calls in the stack? > The only thing I can think of is that we sent SIGQUIT twice. > That's probably bad --- is there any obvious path through > the postmaster that would do that? > > The other thought is that quickdie should block signals before > starting to do anything.
Right. This would actually already work because a signal is blocked while its handler runs, except that we start quickdie() with PG_SETMASK(&BlockSig); which blocks everything except SIGQUIT. That should probably be fixed in any case. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
