Frank Kurzawa <fkurzawa@topazsoftware.com> writes:
> Let's assume that there is a bug in hibernate that is causing it to
> start a transaction behind my back. I'm trying to understand what
> footprints it would leave and I see three possibilities:
> a) It later commits the transaction behind my back
> b) It later rolls back the transaction behind my back
> c) It just leaves the transaction uncommitted/unrolledback/just
> dangling out there.
> ...
> That leaves (c): What would this look like?
> If I do a 'ps -efl' should I find a postgres process in a particular
> state? ('idle waiting on transaction', 'idle in transaction', or
> something else)?
"idle in transaction" would be the usual state in such a case.
> Should there be some other footprints lying around that I can look at?
> Some record of the pending transaction in some postgres system tables?
pg_locks will show an entry with (IIRC) an ExclusiveLock on a
transaction number for each open transaction.
You could also enable query logging and just look for begin/commit commands.
regards, tom lane