Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 24A5A64FD33 for ; Tue, 30 Dec 2008 15:57:03 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 76931-01 for ; Tue, 30 Dec 2008 15:57:00 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 2C4C964FCE2 for ; Tue, 30 Dec 2008 15:57:00 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id mBUJuwEB029256; Tue, 30 Dec 2008 14:56:58 -0500 (EST) To: "Scott Marlowe" cc: "Bhujbal, Santosh" , pgsql-admin@postgresql.org Subject: Re: postgres block_size problem In-reply-to: References: <3BD53621E5C8E54594130AF5459379EE08D80D41@exchindia4.starentnetworks.com> Comments: In-reply-to "Scott Marlowe" message dated "Tue, 30 Dec 2008 11:51:50 -0700" Date: Tue, 30 Dec 2008 14:56:58 -0500 Message-ID: <29255.1230667018@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/204 X-Sequence-Number: 31037 "Scott Marlowe" writes: > On Tue, Dec 30, 2008 at 5:28 AM, Bhujbal, Santosh > 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