| From: | Tom Dunstan <pgsql(at)tomd(dot)cc> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Current enums patch |
| Date: | 2007-04-01 22:45:01 |
| Message-ID: | 461035ED.2020800@tomd.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane wrote:
> The null Datum itself obviously doesn't carry that info, but the
> expression tree does, and there are provisions for letting functions
> retrieve that info --- see get_fn_expr_rettype and get_fn_expr_argtype.
Hmm. I vaguely remember that there was some feeling that the PLs
wouldn't always fill out the FmgrInfo struct, but perhaps that was just
the case with I/O functions.
>> ... could we
>> have a special rule that would look for e.g. a regtype as the first
>> parameter if the return type is generic and there are no generic parameters?
>
> I thought about that too but don't like it much. The problem is mainly
> that it can only work for a constant regtype parameter.
OK, I give up. :) Why?
Thanks
Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-04-01 23:20:37 | Re: Current enums patch |
| Previous Message | Greg Smith | 2007-04-01 22:16:28 | Re: bgwriter stats |