From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "Bhujbal, Santosh" <sbhujbal(at)starentnetworks(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: postgres block_size problem |
Date: | 2008-12-30 19:56:58 |
Message-ID: | 29255.1230667018@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Tue, Dec 30, 2008 at 5:28 AM, Bhujbal, Santosh
> <sbhujbal(at)starentnetworks(dot)com> wrote:
>> SQL execution failed, Internal error. SQL Statement: (COPY command failed
>> with error: ERROR: row is too big: size 8200, maximum size 8136)
> Hmmm. What exactly are you trying to insert into what? Normally when
> you see something like this it's an index on a text field that causes
> this type of problem.
It's not an index because the error message would say so. Evidently
it's a row that TOAST is unable to squeeze down to a workable size,
which suggests a very large number of columns. I'd suggest rethinking
the table schema ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-12-30 20:08:45 | Re: postgres block_size problem |
Previous Message | Scott Marlowe | 2008-12-30 18:58:15 | Re: Context-switch storm in 8.1.15 |