Re: CALL and named parameters

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Thursday, August 7, 2025, Dominique Devienne <ddevienne(at)gmail(dot)com> wrote:
>> What's not nice is in the way it failed IMHO. I guess I persist it's
>> not a user friendly message :)

> Then write the error message you would have liked to see.

The message presumably was like

ERROR: procedure ... does not exist
HINT: No procedure matches the given name and argument types. You might need to add explicit type casts.

That HINT hasn't been updated since we added named arguments, but
"argument names don't match" is now also a possible failure reason.
The simplest possible change would be, say,

HINT: No procedure matches the given name and argument names/types. You might need to add explicit type casts.

Not sure if that's good enough, but the matching rules are
complex enough that it'd be hard to be definitive about
the argument name being the problem.

regards, tom lane