From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | "Andreas Kretschmer *EXTERN*" <akretschmer(at)spamfence(dot)net>, pgsql-general(at)postgresql(dot)org, genesup(at)gmail(dot)com |
Subject: | Re: ERROR: row is too big: size 8176, maximum size 8160 |
Date: | 2010-03-05 08:31:40 |
Message-ID: | dcc563d11003050031t44e8521aj7ac09cdcdd2f4f38@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Mar 5, 2010 at 12:55 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2010-03-05 09:00:06 | Re: Failed to run initdb: 128 |
Previous Message | Craig Ringer | 2010-03-05 08:26:46 | Re: Optimizations |