| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb_delete not documented |
| Date: | 2015-12-07 03:49:15 |
| Message-ID: | 31520.1449460155@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> I see. The reference from pg_operator to pg_proc is by OID rather than
> function name, so I didn't find them. Is that because the function is
> overloaded?
Yeah, I suppose so --- regproc can't resolve overloaded function names.
> It's kind of odd that these are the only operators (at
> first glance) that are set up like that.
I think the customary thing when creating functions meant as operator
support is to give them unique names. These weren't done that way ...
I wasn't involved, but I wonder whether there was uncertainty as to
whether these should be documented as functions or operators.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2015-12-07 05:25:45 | Re: Foreign join pushdown vs EvalPlanQual |
| Previous Message | Peter Eisentraut | 2015-12-07 03:44:46 | Re: jsonb_delete not documented |