Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id BEDCC9FB466 for ; Mon, 21 May 2007 20:29:12 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 08199-04 for ; Mon, 21 May 2007 20:29:08 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 10A9A9FB407 for ; Mon, 21 May 2007 20:29:07 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4LNT588000193; Mon, 21 May 2007 19:29:05 -0400 (EDT) To: "Peter Koczan" cc: pgsql-admin Subject: Re: trouble restarting a server In-reply-to: <4544e0330705211457k30c0cd40oec47e830a0791a9d@mail.gmail.com> References: <4544e0330705211457k30c0cd40oec47e830a0791a9d@mail.gmail.com> Comments: In-reply-to "Peter Koczan" message dated "Mon, 21 May 2007 16:57:28 -0500" Date: Mon, 21 May 2007 19:29:05 -0400 Message-ID: <192.1179790145@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/214 X-Sequence-Number: 25534 "Peter Koczan" writes: > [ lots of processes stuck in "notify interrupt" code ] That's weird. If it's still in that state, or if you can reproduce it, could you attach to a few of those processes with gdb and get stack traces? Looking at the async.c code, an obvious candidate is that that routine tries to take ExclusiveLock on pg_listener --- so if something had managed to exit without releasing a lock on that table, hangups could be expected. But if that were the case, you'd think the process status lines would include "waiting". My guess is they're blocked on something lower-level than a table lock, but without a stack trace it's hard to guess what. Which PG release is this exactly? regards, tom lane