AW: Coping with 'C' vs 'newC' function language names - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: Coping with 'C' vs 'newC' function language names
Date
Msg-id 11C1E6749A55D411A9670001FA687963368127@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Coping with 'C' vs 'newC' function language names
Next
From: Bruce Momjian
Date:
Subject: Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)