From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Koczan <pjkoczan@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: trouble restarting a server
Date: Mon, 21 May 2007 19:29:05 -0400
Message-ID: <192.1179790145@sss.pgh.pa.us> (raw)
In-Reply-To: <4544e0330705211457k30c0cd40oec47e830a0791a9d@mail.gmail.com>
References: <4544e0330705211457k30c0cd40oec47e830a0791a9d@mail.gmail.com>
"Peter Koczan" <pjkoczan@gmail.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, pjkoczan@gmail.com
Subject: Re: trouble restarting a server
In-Reply-To: <192.1179790145@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox