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 EAA13350 for ; Sat, 22 Apr 2000 04:58:12 -0400 (EDT) (envelope-from wieck@debis.com) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@postgresql.org id m12ivdz-0003knC; Sat, 22 Apr 100 10:52 MET DST Message-Id: From: wieck@debis.com (Jan Wieck) Subject: Re: TOAST (was: BLOB) In-Reply-To: <23685.956357662@sss.pgh.pa.us> from Tom Lane at "Apr 21, 2000 06:54:22 pm" To: Tom Lane Date: Sat, 22 Apr 2000 10:52:03 +0200 (CEST) CC: Peter Eisentraut , Jan Wieck , pgsql-sql@postgresql.org Reply-To: Jan Wieck X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200004/252 Tom Lane wrote: > I'd like to think that we can fold the TOAST support into the > argument-access macros that I plan to be defining for the fmgr rewrite. > See previous rants on this subject, eg 14-Jun-99, 23-Oct-99 (in > pgsql-hackers archives). So we need to fold the VARATT_... macro's I'm using now into the FMGR_... macros. Or define the macro's you want now. > Net result for user-defined-datatype authors will be "if you revise > your routines, they will be easier to read, more portable, and will > support TOASTed values. If you don't, they'll still work about as > well (or poorly) as they did before." Sorry, but that ain't true. Making an existing type toastable means that all functions, receiving that type need to be revised. 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) #