Re: question about new fmgr in 7.1 snapshots

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Wieck <janwieck(at)yahoo(dot)com>
Cc: Jeff Hoffmann <jeff(at)propertykey(dot)com>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: question about new fmgr in 7.1 snapshots
Date: 2000-10-23 15:30:56
Message-ID: 8717.972315056@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jan Wieck <janwieck(at)Yahoo(dot)com> writes:
> Tom Lane wrote:
>> Jeff Hoffmann <jeff(at)propertykey(dot)com> writes:
>>>> my question is whether i should change the function to use the new fmgr
>>>> type of definition or if it's only for internal functions.
>>
>> Up to you. If you need any of the new features (like clean handling
>> of NULLs) then convert. If you were happy with the old way, no need.

> Are you sure on that? Doesn't TOAST mean that any user
> defined function recieving variable size attributes must
> expect them now to be compressed or stored external and
> change it's access to them going through the untoasting?

If you have a user-defined function that takes a potentially-toasted
argument, you'll have to fix it to detoast its argument. I don't
think it's appropriate to saddle fmgr with that responsibility.

At least in theory, you could detoast the argument without also buying
into the new fmgr notation, but I agree that converting is easier ;-)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-10-23 15:33:33 Re: [COMMITTERS] pgsql/src/test/regress/expected (plpgsql.out inet.out foreign_key.out errors.out)
Previous Message Peter Eisentraut 2000-10-23 15:30:34 Re: [COMMITTERS] pgsql/src/test/regress/expected (plpgsql.out inet.out foreign_key.out errors.out)