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