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

Re: trouble restarting a server

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Peter Koczan" <pjkoczan(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: trouble restarting a server
Date: 2007-05-21 23:29:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
"Peter Koczan" <pjkoczan(at)gmail(dot)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

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

In response to


pgsql-admin by date

Next:From: AndreasDate: 2007-05-22 00:53:09
Subject: Can I restrict backups?
Previous:From: Peter KoczanDate: 2007-05-21 21:57:28
Subject: trouble restarting a server

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