Re: Connection Idle in transaction

> Not block sorry, but the vacuum is not able to free all the row updated
> by other connections.

But each connection shouldn't have any updated rows that haven't been
committed or rolled back.  Now, if you are running some statements against a
connection and then never calling commit/rollback, that's another thing
since you are actually tying up resources then.  But since the driver just
does a 'begin' after any given commit/rollback, there shouldn't be anything
locked by that connection.

David