Yes it was tried with the 701 build (I am almost sure that we also tried
with cvs-head as of 2 weeks back - will check up on that)
We will correct the connection.close() problem - thanks for pointing
And probably (if we still get problems) try the new build 800 driver.
On 2010-09-13 19:27, Samuel Gendler wrote:
> Your error sure looks exactly like the problem that existed when using
> a Reader instead of InputStream with the older driver (701), though
> your description implies a different problem.
> On Mon, Sep 13, 2010 at 7:17 AM, Kris Jurka <books(at)ejurka(dot)com
> <mailto:books(at)ejurka(dot)com>> wrote:
> On Mon, 13 Sep 2010, Kim Bisgaard wrote:
> We are occasionally experiencing problems with our JDBC
> implementation of COPY IN.
> We have cut our program down to the attached example.
> Do you get the failure you've shown from this example? I get
> another failure from the connection being close before the last
> copy thread can complete its write operation. This seems like an
> expected failure, but I can't reproduce yours.
> org.postgresql.util.PSQLException: Database connection failed when
> canceling copy operation
> at org.postgresql.copy.CopyManager.copyIn(CopyManager.java:150)
> at org.postgresql.copy.CopyManager.copyIn(CopyManager.java:126)
> at EvejrDBCopy.run(EvejrDBCopy.java:34)
> We use PostgreSQL 8.4, and JDBC 8.4-702.
> Your stacktrace shows that you are using 8.4-701, not 702. 702
> had some fixes to the copy code when using a Reader, but your code
> shows you are using an InputStream, so those changes shouldn't be
> Kris Jurka
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org
> To make changes to your subscription:
In response to
pgsql-jdbc by date
|Next:||From: Christian Ullrich||Date: 2010-09-14 22:03:44|
|Subject: Patch: SSPI authentication support|
|Previous:||From: Kris Jurka||Date: 2010-09-13 20:07:37|
|Subject: Re: Eager fetch of Array in one tcp connection|