Re: [HACKERS] Trouble with COPY IN

From: Kris Jurka <books(at)ejurka(dot)com>
To: James William Pye <lists(at)jwp(dot)name>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Matthew Wakeling <matthew(at)flymine(dot)org>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Maciek Sakrejda <msakrejda(at)truviso(dot)com>, Samuel Gendler <sgendler(at)ideasculptor(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [HACKERS] Trouble with COPY IN
Date: 2010-08-09 18:49:04
Message-ID: alpine.BSO.2.00.1008091447440.25873@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

On Sat, 7 Aug 2010, Kris Jurka wrote:

> On Fri, 6 Aug 2010, James William Pye wrote:
>
>> I think there's a snag in the patch:
>>
>> postgres=# COPY data FROM '/Users/jwp/DATA.bcopy' WITH BINARY;
>> ERROR: row field count is -1, expected 1
>> CONTEXT: COPY data, line 4
>>
>> Probably a quick/small fix away, I imagine.
>
> Hmm, not quite sure why that is. That seems to imply that it's not using V3
> protocol, but I thought binary copy could only be used with the V3 protocol.
> In any case, I think this new patch is more bulletproof.
>

Oh, duh. It's a server side copy not going through the client at all.
Here's a hopefully final patch.

Kris Jurka

Attachment Content-Type Size
binary-copy-end-v4.patch text/plain 1.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-08-09 18:49:15 Re: dynamically allocating chunks from shared memory
Previous Message Robert Haas 2010-08-09 18:48:53 Re: dynamically allocating chunks from shared memory

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2010-08-10 17:56:27 Re: 9.0 Driver
Previous Message Donald Fraser 2010-08-09 16:58:08 Re: Java proxies connection to postgres