On 13 April 2011 21:57, Donald Fraser wrote:
> Technically yes. When performing a read on the socket you get -1 indicating
> EOF or remote socket closed. You don't get an IO error.
> The difficult part is what was the client doing when the server closes the
> socket?
> If the client wasn't doing
Sriram Dandapani wrote:
Autocommit is set to off once a connection is obtained from the jboss
pool. It is turned back on when it is closed (so that any idle
transactions are committed).
Don't know what to suggest then -- if autocommit is off then the JDBC
driver should be sending BEGIN before
Sriram Dandapani wrote:
The target table has triggers that route data to appropriate tables. The
tables to which data is routed has check constraints that do further
inserts. (All of this happens in 1 jdbc transaction)
I expect JDBC Batching to generate fewer transactions depending on
batch
Tom Lane wrote:
> This has been discussed before (try the pgsql-jdbc list archives).
> I believe we concluded that an appropriate fix was to not consider the
> cancel request "done" until the client sees the separate connection
> dropped by the postmaster. libpq's cancel functions wait for that t
