Hi Tom,
Good to have you jump in.
The answer to your question (what JDBC version) is:
postgresql-8.1-404.jdbc3.jar
and the postgres version is: 8.2.4
I just downloaded postgresql-8.2-506.jdbc3.jar and
will go ahead and recompile the app over the weekend
with this one.
Aside from that, can this be caused by many deleted
rows from tables (and having neglected to vacuum)?
Tena Sakai
(tsakai@gallo.ucsf.edu)
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Fri 11/9/2007 3:03 PM
To: Scott Marlowe
Cc: Tena Sakai; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] idle in transaction...unexpected EOF on client connection
"Scott Marlowe" <scott.marlowe@gmail.com> writes:
> Hmmm. Well, when you see an error like unexpected EOF on client
> connection then that means that the client "disappeared" without
> closing the connection, or the network connection went away.
More specifically, the client didn't send the expected "terminate session"
message before dropping the network connection.
I seem to recall that old versions of the JDBC driver had a bad habit
of not sending Terminate --- what JDBC version are you using?
regards, tom lane
