I see that every once in a while I get an Idle in Transaction that never ends. This eventually becames a problem, as this Idle in Transaction holds AccessShareLocks. Even if it didn't, if I reach the maximum number of transactions my application dies. Is there any way to know what the transaction did in the past so that I can now which particular query causes this problem within my application? Or at least a way to set a timeout to this transactions? The ideal solution would be to avoid it from happening, but at least a timeout would make it less dangerous. -- View this message in context: http://old.nabble.com/Idle-in-Transaction-tp27467427p27467427.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
