Re: Synchronisation problems in COPY IN
От | Samuel Gendler |
---|---|
Тема | Re: Synchronisation problems in COPY IN |
Дата | |
Msg-id | AANLkTinv9FMCC7gDTEh2dxammqSTPR7pMB1LuY837UGQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Synchronisation problems in COPY IN (Kris Jurka <books@ejurka.com>) |
Ответы |
Re: Synchronisation problems in COPY IN
|
Список | pgsql-jdbc |
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@ejurka.com> wrote:
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.
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.
org.postgresql.util.PSQLException: Database connection failed when canceling copy operation
at org.postgresql.core.v3.QueryExecutorImpl.cancelCopy(QueryExecutorImpl.java:796)
at org.postgresql.core.v3.CopyOperationImpl.cancelCopy(CopyOperationImpl.java:32)
at org.postgresql.copy.CopyManager.copyIn(CopyManager.java:150)
at org.postgresql.copy.CopyManager.copyIn(CopyManager.java:126)
at EvejrDBCopy.run(EvejrDBCopy.java:34)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 relevent.We use PostgreSQL 8.4, and JDBC 8.4-702.
Kris Jurka
--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
В списке pgsql-jdbc по дате отправления: