From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Bhujbal, Santosh <sbhujbal@starentnetworks.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: postgres block_size problem
Date: Tue, 30 Dec 2008 14:56:58 -0500
Message-ID: <29255.1230667018@sss.pgh.pa.us> (raw)
In-Reply-To: <dcc563d10812301051s7ca6b391q132a5194820d8269@mail.gmail.com>
References: <3BD53621E5C8E54594130AF5459379EE08D80D41@exchindia4.starentnetworks.com>
<dcc563d10812301051s7ca6b391q132a5194820d8269@mail.gmail.com>
"Scott Marlowe" <scott.marlowe@gmail.com> writes:
> On Tue, Dec 30, 2008 at 5:28 AM, Bhujbal, Santosh
> <sbhujbal@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 ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, scott.marlowe@gmail.com, sbhujbal@starentnetworks.com
Subject: Re: postgres block_size problem
In-Reply-To: <29255.1230667018@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox