Re: [GENERAL] COPY: row is too big - Mailing list pgsql-general

From Rob Sargent
Subject Re: [GENERAL] COPY: row is too big
Date
Msg-id 7939153b-1b80-6ac0-a184-a6f393b6f962@gmail.com
Whole thread Raw
In response to Re: [GENERAL] COPY: row is too big  (vod vos <vodvos@zoho.com>)
Responses Re: [GENERAL] COPY: row is too big
List 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.

pgsql-general by date:

Previous
From: Tom DalPozzo
Date:
Subject: [GENERAL] requested timeline doesn't contain minimum recovery point
Next
From: Job
Date:
Subject: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22