Re: BUG #16424: COPY Command fails for CSV formath

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "vivek4422(at)gmail(dot)com" <vivek4422(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16424: COPY Command fails for CSV formath
Date: 2020-05-08 14:17:38
Message-ID: CAKFQuwY7uCcmE7sxcP1G=TgpKEzNcvRbjOnEjf2Q0eQkan-SBQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Friday, May 8, 2020, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 16424
> Logged by: Vivek Kamath
> Email address: vivek4422(at)gmail(dot)com
> PostgreSQL version: 10.6
> Operating system: Linux Unix
> Description:
>
> Hi,
>
> I am copying a csv file where the fields are quoted with " and separated
> by
> ,.
> I am using below syntax to copy data using below syntax
>
> psql -c "COPY table_name from filename WITH (FORMAT csv)".
>

Replace that command with something that will handle the poorly structured
csv data you are receiving. COPY is very linear and unforgiving when it
comes to accepting input so you need something that will feed copy that
well-formed data it expects).

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-05-08 15:25:54 BUG #16425: Possible error in full join
Previous Message Fabio Pardi 2020-05-08 14:17:23 Re: pg_dump