Jan Wieck <[EMAIL PROTECTED]> 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
- Re: [HACKERS] CREATE MODULE (was: Coping wit... Philip Warner
- Re: [HACKERS] Coping with 'C' vs 'newC' function language... Jan Wieck
- Re: [HACKERS] Coping with 'C' vs 'newC' function lan... Peter Eisentraut
- Re: [HACKERS] Coping with 'C' vs 'newC' function... Tom Lane
- Re: [HACKERS] Coping with 'C' vs 'newC' func... Bruce Momjian
- Re: [HACKERS] Coping with 'C' vs 'newC' ... Tom Lane
- Re: [HACKERS] Coping with 'C' vs 'newC' ... Thomas Lockhart
- Re: [HACKERS] Coping with 'C' vs 'newC' ... Bruce Momjian
- Re: [HACKERS] Coping with 'C' vs 'newC' ... Hannu Krosing
- Re: [HACKERS] Coping with 'C' vs 'newC' ... Bruce Momjian
- Tom Lane