Re: BUG #15206: Can not import CSV into PostgreSQL

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: miloradkrstevski(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15206: Can not import CSV into PostgreSQL
Date: 2018-05-19 12:55:26
Message-ID: CAKFQuwbZmOF01yF8aOzL4PpyBz0wCzHato+FHjoq5ZH=Zo91Tw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, May 19, 2018 at 4:19 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:

> Hi
>
> 2018-05-19 11:09 GMT+02:00 PG Bug reporting form <noreply(at)postgresql(dot)org>:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 15206
>> Logged by: Milorad Krstevski
>> Email address: miloradkrstevski(at)gmail(dot)com
>> PostgreSQL version: 10.4
>> Operating system: Ubuntu 18.04 LTS x64
>> Description:
>>
>> Respected,
>>
>> No matter what I try, I always get the error: ERROR: extra data after last
>> expected column, and can not import CSV into table in PostgreSQL.
>>
>> I am using pgAdmin 4.30, Python 3.6.5, Flask 0.12.2.
>>
>> Can you please point out solution to my problem please?
>>
>
> It is not PostgreSQL bug, so pg_general mailing list will be better.
>
> PostgreSQL is very strict about CSV format - it looks so some line of CSV
> doc has more columns than target table.
>

​IOW, we cannot help unless you provide both the CSV file and the table
definition.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Milorad Krstevski 2018-05-19 13:57:46 Re: BUG #15206: Can not import CSV into PostgreSQL
Previous Message Pavel Stehule 2018-05-19 11:19:47 Re: BUG #15206: Can not import CSV into PostgreSQL