Brian Cox <brian.cox@ca.com> writes:
> OK. You mentioned strace. It's got a lot of options; any in particular
> that would be useful if this happens again?
I'd just do "strace -p processID" and watch it for a little while.
If it's not hung, you'll see the process issuing kernel calls at
some rate or other.
If it is hung, you'll most likely see something like
semop(...)
and it just sits there. Also, if you see nothing but a series of
select()s with varying timeouts, that would suggest a stuck spinlock
(although I doubt that was happening, as it would eventually timeout
and report a failure).
regards, tom lane