Skip site navigation (1) Skip section navigation (2)

Re: postgres block_size problem

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 (view raw or flat)
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

In response to

Responses

pgsql-admin by date

Next:From: Scott MarloweDate: 2008-12-30 20:08:45
Subject: Re: postgres block_size problem
Previous:From: Scott MarloweDate: 2008-12-30 18:58:15
Subject: Re: Context-switch storm in 8.1.15

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group