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

Re: Postgres 7.4.6 hang in async_notify

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-bugs(at)counterstorm(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Postgres 7.4.6 hang in async_notify
Date: 2005-04-25 22:20:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
pgsql-bugs(at)counterstorm(dot)com writes:
> We have seen this twice.  The first time, it was on a 32 bit Fedora
> Core 3 system during a `postgres stop`.  The stop hung because one of
> the processes was in async_notify and refused to get out.  We were
> unable to do further debugging because the db was in shutdown.  We
> were forced to kill -9 the process.

Next time try attaching to the stuck backend with gdb so you can get
a stack trace.  It's difficult to speculate what could be wrong without
a better-localized idea of where it's hanging.  It'd be a good idea to
rebuild with --enable-debug so that the stack trace will be most useful
when you get it.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Dennis VshivkovDate: 2005-04-26 08:34:51
Subject: BUG #1626: Minimum documented values aren't accepted for all basic integer types
Previous:From: pgsql-bugsDate: 2005-04-25 21:43:31
Subject: Re: Postgres 7.4.6 hang in async_notify

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