Re: ERROR: row is too big: size 8176, maximum size 8160 - Mailing list pgsql-general

From Tom Lane
Subject Re: ERROR: row is too big: size 8176, maximum size 8160
Date
Msg-id 29492.1267795795@sss.pgh.pa.us
Whole thread Raw
In response to Re: ERROR: row is too big: size 8176, maximum size 8160  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-general
Scott Marlowe <scott.marlowe@gmail.com> writes:
> On Fri, Mar 5, 2010 at 12:55 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
>> Or maybe a large column has been modified by
>> ALTER TABLE ... ALTER COLUMN ... SET STORAGE PLAIN

> I thought even then if the backend can't fit it all in 8k it puts text
> out of line.

No, SET STORAGE PLAIN is an absolute override, if I recall the code
correctly.  That seems an unlikely explanation though.  What I'd bet on
is a very large number of non-toastable columns.  A thousand or so
float8's would do it for instance.  But this is all speculation without
seeing the table declaration.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Xpath Index in PostgreSQL
Next
From: Tom Lane
Date:
Subject: Re: need some advanced books on Postgres