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

I see!

Thank you for your quick answer. We have to think if we can rearrange it.

The funny thing is that we have the same number of columns for other
tables which are the same except for stored geometries and those
stores the information without any problem.
That's why I thought maybe is a corruption thing or something

2018-07-11 16:40 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> 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
>