Thread: Additional debugging of idle sessions?

I am experiencing a blocking situation in my database (Postgresql 8.1.8
on Redhat).  When I do a "ps -ef|grep postgres" I see two processing
that are "idle in transaction" and they stay there indefinitely.

I'm running JBoss (the problem is in JBossMQ) and I'm having trouble
pinpointing the location/cause of the block as JBoss doesn't report any
errors or exceptions.  It just sits there.

Is there any way to increase the debug logging or issue a query so that
I could find the actual select statements that are idle?  That would
help me isolate the source of my problem.

Thanks

Mike Goldner <mgoldner@agmednet.com> writes:
> Is there any way to increase the debug logging or issue a query so that
> I could find the actual select statements that are idle?

Huh?  "Idle in transaction" means there *isn't* any active SQL statement
--- those backends are waiting for the next client command.  What you
seem to need is more visibility into the state of your client code,
which I'm afraid we can't help you with.  Possibly you could get useful
help on a JBoss-related list.

            regards, tom lane