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

From Scott Marlowe
Subject Re: ERROR: row is too big: size 8176, maximum size 8160
Date
Msg-id dcc563d11003050031t44e8521aj7ac09cdcdd2f4f38@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: row is too big: size 8176, maximum size 8160  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Responses Re: ERROR: row is too big: size 8176, maximum size 8160  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Re: ERROR: row is too big: size 8176, maximum size 8160  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Fri, Mar 5, 2010 at 12:55 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
> Andreas Kretschmer wrote:
>> > I am using postgresql-8.3.7 and have recently got this error:
>> >
>> > org.postgresql.util.PSQLException: ERROR: row is too big: size 8168,
>> > maximum size 8160
>>
>> Please show us your table definition.
>>
>> Wild guess: you have many, many columns, non-text (INT or something
>> else), and such a row is bigger than 8 KByte, PG can't use TOAST.
>>
>> I think, you should re-design your table, read about normalisation.
>
> Or maybe a large column has been modified by
> ALTER TABLE ... ALTER COLUMN ... SET STORAGE PLAIN
>
> In any case, if you cannot figure out what causes your row to be
> so big, tell us the statements used to create the table and give us
> an idea of what you insert (the whole row is probably too much spam).

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

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Optimizations
Next
From: Richard Huxton
Date:
Subject: Re: Failed to run initdb: 128