| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rick Otten <rotten(at)windfish(dot)net> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14048: copy issues with jsonb |
| Date: | 2016-03-28 17:13:02 |
| Message-ID: | CAKFQuwb0GtzfuQgHe+tS1_w+svSpCfOH8Zur994vJ5yPtgEoJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Mar 28, 2016 at 9:35 AM, Rick Otten <rotten(at)windfish(dot)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.
>
It is not ignored - it is informing COPY that the first line of your input
file is not data but meta-data and thus must be ignored.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | d.j.yotta | 2016-03-28 23:06:32 | BUG #14049: Integer out of range on insert with default id |
| Previous Message | Rick Otten | 2016-03-28 16:35:57 | Re: BUG #14048: copy issues with jsonb |