Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 07F8F474E61 for ; Sun, 3 Nov 2002 19:19:56 -0500 (EST) Received: from varsoon.wireboard.com (www.wireboard.com [216.151.155.101]) by postgresql.org (Postfix) with ESMTP id 8BD44474E44 for ; Sun, 3 Nov 2002 19:19:55 -0500 (EST) Received: from doug by varsoon.wireboard.com with local (Exim 3.35 #1) id 188UyC-00022B-00; Sun, 03 Nov 2002 19:19:56 -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> <20021104011105.A11131@goldfisch.at> From: Doug McNaught Date: 03 Nov 2002 19:19:56 -0500 In-Reply-To: pilsl@goldfisch.at's message of "Mon, 4 Nov 2002 01:11:06 +0100" Message-ID: Lines: 20 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/94 X-Sequence-Number: 32516 pilsl@goldfisch.at writes: > On Fri, Nov 01, 2002 at 08:50:54AM -0500, Doug McNaught wrote: > > > > 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" > > > > I already created the table with 1600 cols of varchar(30) so this > should not be the limit. And the errormessage is clearly talking about > the tuples size. (which should not have such a limit in 7.2.3). Well, it does say "depending on column type". Perhaps it is giving a valid error but the wrong message. The 8k tuple-size limit is definitely gone in modern versions of PG (since 7.1 I believe) so I don't see why that error message should appear. -Doug