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