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

From Tom Lane
Subject Re: Coping with 'C' vs 'newC' function language names
Date
Msg-id 9441.974753792@sss.pgh.pa.us
Whole thread Raw
In response to Re: Coping with 'C' vs 'newC' function language names  (Jan Wieck <janwieck@Yahoo.com>)
List pgsql-hackers
Jan Wieck <janwieck@Yahoo.com> writes:
>     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.  Worst
>     case a dump might reload and anything works fine, but a month
>     later the first toasted value appears  and  the  old-style  C
>     function corrupts the data without a single warning.

>     We need to WARN, WARN and explicitly WARN users of selfmade C
>     functions about this in any possible place!

As of now, not.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: RPM's -fsigned-char (Re: [COMMITTERS] pgsql/src/backend/utils/adt (cash.c))
Next
From: Peter Eisentraut
Date:
Subject: Regression test drivers