David Parker wrote:

>Agreed. I was desperate. It turned out that we had a Java server process
>that was using the 7.4.5 version of the JDBC driver with
>autocommit=false, and Connection.commit() in that version of the driver
>does 
>"commit; begin;" which obviously leaves the postgres process "<IDLE> in
>Transaction" - apparently a well-known issue but I was not aware of it.
>THAT made for a fun weekend.....
>  
>
You should be aware that this causes plenty of other problems than
merely with Slony-I...

IDLE in transaction prevents vacuums from doing anything useful on much
of anything, which will hurt all sorts of applications.