Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id CB6A064FEE7 for ; Tue, 30 Dec 2008 16:08:49 -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 78561-09 for ; Tue, 30 Dec 2008 16:08:46 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mail.postgresql.org (Postfix) with ESMTP id 9ACAB64FDA5 for ; Tue, 30 Dec 2008 16:08:46 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id j4so2999112wah.19 for ; Tue, 30 Dec 2008 12:08:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=Cy21kxEfCXuzKHCnUK7Un7zFwNyul0SwifFRiGcM7ow=; b=ATWx8UI4u8IfBRjMlUn1SKvas6dv4FfjanU4AI+TmfUyR2ZwMERZ1XQwrpaeJjzTiu cOGezBsrcjz16nJm8wrA130eSAG458/XHsaCPWvwHPJ7SpCa5E2ESF/9dECOMGCY9MD1 lAdt1i1LMk0Ui3vc/lraAB84Ka2MUq/dWQsKU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=CXo3MocddIfx4rQ2BQNVQA6v4thp63PB2BiQq4hoGkixWW4uV7/+qJwDb87vG9Xaa/ mzzGEHLnbZa+is4Uxe7npUg+v4uUam7f4uwMjHAn/nnU3tfJU2z42cbhJU5nRqEuLN5N 7N8xhUJKOTPl1M+hxn6qaLtfmcLTyxM/yhRWw= Received: by 10.115.19.16 with SMTP id w16mr9980237wai.51.1230667725548; Tue, 30 Dec 2008 12:08:45 -0800 (PST) Received: by 10.114.132.17 with HTTP; Tue, 30 Dec 2008 12:08:45 -0800 (PST) Message-ID: Date: Tue, 30 Dec 2008 13:08:45 -0700 From: "Scott Marlowe" To: "Tom Lane" Subject: Re: postgres block_size problem Cc: "Bhujbal, Santosh" , pgsql-admin@postgresql.org In-Reply-To: <29255.1230667018@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3BD53621E5C8E54594130AF5459379EE08D80D41@exchindia4.starentnetworks.com> <29255.1230667018@sss.pgh.pa.us> 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/205 X-Sequence-Number: 31038 On Tue, Dec 30, 2008 at 12:56 PM, Tom Lane wrote: > "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 ... 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... :)