Re: COPY: row is too big

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: vod vos <vodvos(at)zoho(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: COPY: row is too big
Date: 2017-01-05 16:31:24
Message-ID: 7939153b-1b80-6ac0-a184-a6f393b6f962@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 01/05/2017 05:44 AM, vod vos wrote:
> I finally figured it out as follows:
>
> 1. modified the corresponding data type of the columns to the csv file
>
> 2. if null values existed, defined the data type to varchar. The null
> values cause problem too.
>
> so 1100 culumns work well now.
>
> This problem wasted me three days. I have lots of csv data to COPY.
>
>
Yes, you cost yourself a lot of time by not showing the original table
definition into which you were trying insert data.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Job 2017-01-05 17:18:53 Postgres 9.6.1 big slowdown by upgrading 8.4.22
Previous Message Merlin Moncure 2017-01-05 16:21:00 Re: Postgresql query HAVING do not work