idle in transaction - Mailing list pgsql-jdbc

From Alexey Yudichev
Subject idle in transaction
Date
Msg-id 8BCBF9DB739F034B87FE7C7D30EAE55C15A6CC@hqex2k.francoudi.com
Whole thread Raw
Responses Multiple open ResultSets not allowed?
Re: idle in transaction
List pgsql-jdbc
It seems that connection.commit() commits current transaction and immediately begins a new one so that connection
statusis always "idle in transaction". During that time no indicies could be created/dropped, no vaccum command can be
issuedetc because of locks I suppose.  
  I use PostgreSQL 7.1 and tried 7.2 drivers and 7.3 drivers (with option compatible=7.1).
  Is there anything that can be done to allow creating index without restarting the connection pool?

pgsql-jdbc by date:

Previous
From: Tim Farrell
Date:
Subject: Re: embedding PostgreSQL in a Java application
Next
From: Jeff Kolesky
Date:
Subject: Multiple open ResultSets not allowed?