Skip site navigation (1) Skip section navigation (2)

Re: Trouble with COPY IN

From: Matthew Wakeling <matthew(at)flymine(dot)org>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Maciek Sakrejda <msakrejda(at)truviso(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Trouble with COPY IN
Date: 2010-07-19 13:22:52
Message-ID: alpine.DEB.2.00.1007191421110.8895@aragorn.flymine.org (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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?"

In response to

pgsql-hackers by date

Next:From: Oleg BartunovDate: 2010-07-19 13:26:47
Subject: Re: Incorrect FTS result with GIN index
Previous:From: Matthew WakelingDate: 2010-07-19 11:35:16
Subject: Re: Trouble with COPY IN

pgsql-jdbc by date

Next:From: Matthew WakelingDate: 2010-07-19 14:11:06
Subject: Re: Trouble with COPY IN
Previous:From: Matthew WakelingDate: 2010-07-19 11:35:16
Subject: Re: Trouble with COPY IN

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group