Received: from nibbler.toppoint.de (LaForge.toppoint.de [195.244.243.6]) by hub.org (8.9.3/8.9.3) with SMTP id VAA27838 for ; Wed, 27 Oct 1999 21:35:52 -0400 (EDT) (envelope-from feki.toppoint.de!marten@toppoint.de) Received: by nibbler.toppoint.de (Smail3.1.29.1) id ; Thu, 28 Oct 99 03:33 MET DST Received: (from marten@localhost) by feki.phoenix-edv.netzservice.de (8.9.3/8.9.3) id IAA16655; Wed, 27 Oct 1999 08:41:02 +0200 From: marten@feki.toppoint.de Message-Id: <199910270641.IAA16655@feki.phoenix-edv.netzservice.de> Subject: Re: [INTERFACES] 8k limit In-Reply-To: <23186.940954609@sss.pgh.pa.us> from Tom Lane at "Oct 26, 1999 12:16:49 pm" To: tgl@sss.pgh.pa.us (Tom Lane) Date: Wed, 27 Oct 1999 08:41:02 +0200 (CEST) Cc: Michael.Ansley@intec.co.za, stuart@comodo.net, pgsql-interfaces@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > There has been discussion of fixing this, eg by making a subdirectory > tree for LOs, but I'd rather see us put our effort into eliminating > the tuple length limit. > This would be very nice - because this also means to get SQL statements that may really be 8k long ! Perhaps you all remember a rather complex view statement I posted here some days ago, where postgresql said something like "rule too large" and this seems to be a limitation for me. Actually as a user one does not know when this limit is reached by the system. All "we" (the users :-)) know about the 8192 byte limit of an SQL statement, but this is not the whole truth. Marten