[EMAIL PROTECTED] 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 shutdow
In message <[EMAIL PROTECTED]>, Alvaro Herrera writes:
On Mon, Apr 25, 2005 at 03:42:35PM -0400, [EMAIL PROTECTED] wrote:
> The way the notify gets called is a bit convoluted. Our C program
> performs an insert in table T. Some triggers run doing all sorts of
> stuff in the
On Mon, Apr 25, 2005 at 03:42:35PM -0400, [EMAIL PROTECTED] wrote:
> The way the notify gets called is a bit convoluted. Our C program
> performs an insert in table T. Some triggers run doing all sorts of
> stuff in the background involving changes to other tables. Under some
> circumstances, a
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
