From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Jan Wieck <wieck(at)debis(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: TOAST (was: BLOB) |
Date: | 2000-04-22 08:52:03 |
Message-ID: | m12ivdz-0003knC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 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(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2000-04-22 10:02:51 | Re: question on UPDATE rules |
Previous Message | Jan Wieck | 2000-04-22 08:45:33 | Re: TOAST (was: BLOB) |