Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 290D2474E53
	for <pgsql-general@postgresql.org>;
	Fri,  1 Nov 2002 08:50:53 -0500 (EST)
Received: from varsoon.wireboard.com (www.wireboard.com [216.151.155.101])
	by postgresql.org (Postfix) with ESMTP id AA212474E44
	for <pgsql-general@postgresql.org>;
	Fri,  1 Nov 2002 08:50:52 -0500 (EST)
Received: from doug by varsoon.wireboard.com with local (Exim 3.35 #1)
	id 187cCM-0006ay-00; Fri, 01 Nov 2002 08:50:54 -0500
To: pilsl@goldfisch.at
Cc: pgsql-general@postgresql.org
Subject: Re: 7.2.3: tuple is too big (max 8136)
References: <20021101143348.A7426@goldfisch.at>
From: Doug McNaught <doug@mcnaught.org>
Date: 01 Nov 2002 08:50:54 -0500
In-Reply-To: pilsl@goldfisch.at's message of "Fri, 1 Nov 2002 14:33:48 +0100"
Message-ID: <m37kfx9z5t.fsf@varsoon.wireboard.com>
Lines: 23
User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200211/13
X-Sequence-Number: 32435

pilsl@goldfisch.at writes:

> I got this error on older versions and was told to
> upgrade. Unfortunately I run into the very same error with 7.2.3.
> 
> I have a table with 1600 cols (for testing) and insert one row into
> it which results in this error:

It's possible you are hitting the maximum column limit rather than the
tuple size limit.  The FAQ list the max columns in a table as:

"250-1600 depending on column types"

So try a tuple of the same size but fewer columns and see if that's
the issue.

> I searched my whole systems for old libraries from a previous version
> but I'm quite sure that my upgrade was quite a clean and successful
> one...

I'm sure you're right but it's always good to double-check.  ;)

-Doug