Re: TOAST (was: BLOB) - Mailing list pgsql-sql

From wieck@debis.com (Jan Wieck)
Subject Re: TOAST (was: BLOB)
Date
Msg-id m12ivdz-0003knC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: TOAST (was: BLOB)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TOAST (was: BLOB)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
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
needto 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) #




pgsql-sql by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: TOAST (was: BLOB)
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: question on UPDATE rules