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 TAA97143 for ; Fri, 10 Dec 1999 19:37:06 -0500 (EST) (envelope-from wieck@debis.com) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@postgreSQL.org id m11waPv-0003kGC; Sat, 11 Dec 99 01:29 MET Message-Id: From: wieck@debis.com (Jan Wieck) Subject: Re: [SQL] Dilema. To: wieck@debis.com Date: Sat, 11 Dec 1999 01:29:42 +0100 (MET) Cc: mitch@venux.net, pgsql-sql@postgreSQL.org Reply-To: wieck@debis.com (Jan Wieck) In-Reply-To: from "Jan Wieck" at Dec 11, 99 01:03:35 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text I wrote: > Look at this: > > pgsql=> select key, length(content) from bttest; > key | length > -----+-------- > 1 | 3 > 2 | 9 > 4 | 135840 > (3 rows) Rereading my own comment, I just realized that it would be possible to add a real BIG text type with a slightly different technique. This would require another (not syscached) pg_ relation plus support in heap access and some other parts. And it would be a DEFINITELY NOT indexable type. Also it would be subject to get removed someday after we implemented large tuples. But it would drop the pressure from the large tuple item close to zero IMHO. So if I can implement it in a way, that ensures it is easily removable again, why not? 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) #