Re: BUG #14048: copy issues with jsonb - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #14048: copy issues with jsonb
Date
Msg-id CAKFQuwb0GtzfuQgHe+tS1_w+svSpCfOH8Zur994vJ5yPtgEoJg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14048: copy issues with jsonb  (Rick Otten <rotten@windfish.net>)
List pgsql-bugs
On Mon, Mar 28, 2016 at 9:35 AM, Rick Otten <rotten@windfish.net> wrote:

> So the problem is a column order thing and not something buried in my
> jsonb data.  Mr. Johnston was very helpful in resolving this.
>
> Apparently when you do a "copy from with csv header", the 'header' phrase
> is ignored in spite of the keyword being present in your statement.
>
=E2=80=8BIt is not ignored - it is informing COPY that the first line of yo=
ur input
file is not data but meta-data and thus must be ignored.=E2=80=8B

There are external utilities available that make doing the whole copy thing
much more user-friendly.  Given their existence not much effort is expended
trying to enhance the native copy facilities beyond making it extremely
fast for bulk loading well-specified data.

David J.

pgsql-bugs by date:

Previous
From: Rick Otten
Date:
Subject: Re: BUG #14048: copy issues with jsonb
Next
From: d.j.yotta@gmail.com
Date:
Subject: BUG #14049: Integer out of range on insert with default id