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

Re: Trouble with COPY IN

From: Kris Jurka <books(at)ejurka(dot)com>
To: Maciek Sakrejda <msakrejda(at)truviso(dot)com>
Cc: Matthew Wakeling <matthew(at)flymine(dot)org>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Trouble with COPY IN
Date: 2010-07-16 17:41:13
Message-ID: alpine.BSO.2.00.1007161336490.32040@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-jdbc

On Fri, 16 Jul 2010, Maciek Sakrejda wrote:

> Could it be that COPY is erroring out, and then the driver tries to
> end it anyway, causing the error?

That seems likely.  What's probably necessary to reproduce this is a 
failure at the end of the data stream.  An early error will be received 
and processed normally, but an error at the end will be buffered and the 
driver will think everything succeeded and try to end the copy not knowing 
that it has already failed.  I think we'd need to call the blocking 
version of processCopyResults prior to endCopy to avoid this misleading 
error.

Kris Jurka

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2010-07-16 17:49:16
Subject: Re: SHOW TABLES
Previous:From: Maciek SakrejdaDate: 2010-07-16 17:32:01
Subject: Re: Trouble with COPY IN

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2010-07-16 18:06:21
Subject: Re: Trouble with COPY IN
Previous:From: Maciek SakrejdaDate: 2010-07-16 17:32:01
Subject: Re: Trouble with COPY IN

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