| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, Jan Wieck <janwieck(at)Yahoo(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: Coping with 'C' vs 'newC' function language names |
| Date: | 2000-11-17 17:02:19 |
| Message-ID: | 11C1E6749A55D411A9670001FA687963368127@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Just successfully loading an old-style C function doesn't
> > guarantee that it works anyway. I pointed out before that the
> > changes due to TOAST require each function that takes
> > arguments of varlen types to expect toasted values.
>
> Couldn't the function handler detoast the values before handing them to
> the function? That would be slower, but it would allow people to continue
> to use the "simpler" interface.
Are there really that many things you can do with a toasted value ?
Off hand I can only think of equality functions. All others should need
a detoasted value anyways.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-11-17 17:16:06 | Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) |
| Previous Message | Tom Lane | 2000-11-17 16:52:12 | Re: Coping with 'C' vs 'newC' function language names |