Re: Trouble with COPY IN - Mailing list pgsql-jdbc

From Matthew Wakeling
Subject Re: Trouble with COPY IN
Date
Msg-id alpine.DEB.2.00.1007191421110.8895@aragorn.flymine.org
Whole thread Raw
In response to Re: Trouble with COPY IN  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc
On Fri, 16 Jul 2010, Kris Jurka wrote:
> 2) The protocol docs say that after an error, CopyData, CopyDone, and
> CopyFail messages are ignored, so they wouldn't be causing this error.

The exception I receive isn't produced by the server. It is caused by the
client losing its own lock on the database connection. Surely the place
where the lock gets thrown away would be caused by a separate server
error, and should have been reported?

Matthew

--
So, given 'D' is undeclared too, with a default of zero, C++ is equal to D.
  mnw21, commenting on the "Surely the value of C++ is zero, but C is now 1"
  response to "No, C++ isn't equal to D. 'C' is undeclared [...] C++ should
  really be called 1" response to "C++ -- shouldn't it be called D?"

pgsql-jdbc by date:

Previous
From: Chris Wareham
Date:
Subject: Re: Questions about Listen/Notify mechanism
Next
From: Matthew Wakeling
Date:
Subject: Re: Trouble with COPY IN