Re: row is too big: size 8168, maximum size 8160

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mario De Frutos Dieguez <mariodefrutos(at)gmail(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: row is too big: size 8168, maximum size 8160
Date: 2018-07-11 14:40:28
Message-ID: 19464.1531320028@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Mario De Frutos Dieguez <mariodefrutos(at)gmail(dot)com> writes:
> I've found this error message and it's driving me crazy.

> I have a table with 790 numeric columns, I'm trying to make an INSERT INTO
> x SELECT... and in the same column/s I'm getting this message.

You can either rethink your data representation (maybe you could put a
bunch of those values into an array?) or recompile/re-initdb with a
larger value of BLCKSZ. I'd favor the former --- 790 columns is too many.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2018-07-11 14:43:06 Re: invalid value for parameter "client_encoding": "ISO_8859_8"
Previous Message Mariel Cherkassky 2018-07-11 14:38:01 upgrading postgresql cluster(3 nodes) to v10 without DOWNTIME