It finally reoccurred. Here's what I got from attaching to those processes
from gdb. I attached with the postmaster binary, let me know if I should use
something else.
vero(su): ps axvw | grep notify
24556 ?Ss 0:03 0 3265 41262 29672 0.7 postgres: jerel
csdb chef(36275) notify
The release is 8.2.4. I haven't been able to reproduce the condition yet,
but I will send along stack traces as soon as I can. I have this strange
feeling that it's only going to happen when I find a reason to make a
restart-worthy config change.
Peter
On 5/21/07, Tom Lane <[EMAIL PROTECTED]> wr
"Peter Koczan" <[EMAIL PROTECTED]> 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
Hi all, I'm having some trouble restarting a long-running server. Basically,
pg_ctl can't kill any processes waiting on a notify interrupt. Here's what
happened after trying a "stop -m fast"
[EMAIL PROTECTED] ~]# ps axvw | grep post
3606 ?S 3:30 23 3260 41575 6644 0.1 /usr/bin/
