Re: CALL and named parameters
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Dominique Devienne <ddevienne@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2025-08-07T13:30:30Z
Lists: pgsql-general
On Thursday, August 7, 2025, Dominique Devienne <ddevienne@gmail.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. > > Can you overload a function solely by changing an argument name? No, the signature is only the name and input argument types. > If not, as I suspect, then function lookup doesn't strictly depend on > argument names (like in C++). > So the function did exist, with the correct "signature" (ignoring > argument names). > And I was "just" using the wrong arg-name. That tripped me up. How is it “just” an argument name when you are using named argument syntax? David J.