| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CALL and named parameters |
| Date: | 2025-08-07 14:42:15 |
| Message-ID: | 1569525.1754577735@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dominique Devienne <ddevienne(at)gmail(dot)com> writes:
> But still, arg names are not part of the signature.
> So they should be checked after the fact.
No, that's not how it works. David's comment about signature
reflects the fact that the primary key of pg_proc is name +
schema + input argument types. Arg names are independent of
that and actually have to be checked before we consider argument
type matching, because they help determine which input argument
is which.
(There was considerable debate when we added output arguments
and argument names about whether pg_proc's primary key should
be extended. We ended up not, but it was a judgment call.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-08-07 16:03:58 | Re: Libpq.dll |
| Previous Message | Dominique Devienne | 2025-08-07 14:39:03 | Re: CALL and named parameters |