Re: CALL and named parameters

On Fri, Aug 8, 2025 at 1:33 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> writes:
> > ## Dominique Devienne (ddevienne(at)gmail(dot)com):
> >> dd_v185=> call "Epos-DBA".db_grant_connect_to(grantee_role => 'dd_joe');
> >> ERROR: procedure Epos-DBA.db_grant_connect_to(grantee_role =>
> >> unknown) does not exist
> >> LINE 1: call "Epos-DBA".db_grant_connect_to(grantee_role => 'dd_joe'...
>
> > There's the problem: "unknown" type - consider that string there as
> > "too flexible", it can be coerced into too many types, so the error
> > says "unknown".
>
> No, the issue is that the procedure's named parameter is not named
> "grantee_role" but something else. We'd have coerced the unknown
> parameter just fine, except that we never considered this procedure
> as a valid match at all.

That. And it failed just the same with a ::name cast, so no "unknown"
type there.
And in all of that, there's a single "Epos-DBA".db_grant_connect_to(...).
So it's not like the "candidates" are a large set. --DD