| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <janwieck(at)Yahoo(dot)com> |
| Cc: | Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Coping with 'C' vs 'newC' function language names |
| Date: | 2000-11-20 20:56:32 |
| Message-ID: | 9441.974753792@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Wieck <janwieck(at)Yahoo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-11-20 22:03:20 | Regression test drivers |
| Previous Message | Lamar Owen | 2000-11-20 20:05:28 | Re: RPM's -fsigned-char (Re: [COMMITTERS] pgsql/src/backend/utils/adt (cash.c)) |