From: | vod vos <vodvos(at)zoho(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: COPY: row is too big |
Date: | 2017-01-02 17:03:07 |
Message-ID: | 159602272ba.dc1def6214224.2007227761535212546@zoho.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
You know, the csv file was exported from other database of a machine, so I really dont want to break it for it is a hard work. Every csv file contains headers and values. If I redesign the table, then I have to cut all the csv files into pieces one by one.
---- On 星期一, 02 一月 2017 08:21:29 -0800 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote ----
vod vos <vodvos(at)zoho(dot)com> writes:
> When I copy data from csv file, a very long values for many columns (about 1100 columns). The errors appears:
> ERROR: row is too big: size 11808, maximum size 8160
You need to rethink your table schema so you have fewer columns.
Perhaps you can combine some of them into arrays, for example.
JSON might be a useful option, too.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
To make changes to your subscription:
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-01-02 17:13:45 | Re: COPY: row is too big |
Previous Message | Vincent Veyron | 2017-01-02 16:31:19 | Re: Difficulty modelling sales taxes |