On Tue, Dec 30, 2008 at 12:56 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "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 ...
Oh yeah, that does sound like wide tables. Yeah, it's likely highly
denormalized or something like that.
I thought the error message was different, but I haven't seen it in years... :)
In response to
pgsql-admin by date
|Next:||From: Carol Walter||Date: 2008-12-30 20:53:37|
|Subject: Re: ssl database connection problems...|
|Previous:||From: Tom Lane||Date: 2008-12-30 19:56:58|
|Subject: Re: postgres block_size problem |