Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.3/8.9.3) with SMTP id CAA00206 for ; Mon, 13 Dec 1999 02:36:42 -0500 (EST) (envelope-from wieck@debis.com) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@postgreSQL.org id m11xPvF-0003kGC; Mon, 13 Dec 99 08:29 MET Message-Id: From: wieck@debis.com (Jan Wieck) Subject: Re: [SQL] Problem copying polygon data into a table To: brent.wood@blazemail.com (Brent Wood) Date: Mon, 13 Dec 1999 08:29:29 +0100 (MET) Cc: pgsql-sql@postgreSQL.org Reply-To: wieck@debis.com (Jan Wieck) In-Reply-To: <385493F8.D8D17B68@blazemail.com> from "Brent Wood" at Dec 13, 99 07:36:40 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text > The polygon has about 800 vertices (& is relatively small as some of the > polygons in my dataset go). > > Trying to copy this into the table generates the error msg: > > ERROR: Tuple is too big: size 12892 It is a very old limitation, that one row (including the systems per row information and ALL attribute values) cannot exceed 8K - pageheader. 800 vertices is 1600 double precision floats is 12800 bytes. We actually discuss how to tackle that problem in a future release. And that far we know about a solution that could make your problem go away. What we don't have is a consensus on, and implementation of this solution. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #========================================= wieck@debis.com (Jan Wieck) #