On Tue, Dec 30, 2008 at 12:56 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > "Scott Marlowe" <scott.marl...@gmail.com> writes: >> On Tue, Dec 30, 2008 at 5:28 AM, Bhujbal, Santosh >> <sbhuj...@starentnetworks.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... :) -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
