public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dominique Devienne <[email protected]>
To: Tom Lane <[email protected]>
Cc: David G. Johnston <[email protected]>
Cc: Pavel Stehule <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: CALL and named parameters
Date: Thu, 7 Aug 2025 16:26:34 +0200
Message-ID: <CAFCRh-_zu2hQpACVQaxGiuCFe5FWnEWQCb6TRCa-zfC539mF0g@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAFCRh-_iLoUtMAtyunw_-O6sgpWo04sOmB38MUVNpuQVSkL_0Q@mail.gmail.com>
	<CAFj8pRCyW4E5OnZDGvk_YnPqaS_PfK-VKJOKGndC-gtAtDOtBw@mail.gmail.com>
	<CAFCRh-9XkFS==OwSB6jgY84L5d4PkV_Y9MxLgk=NVx0Z8W3o_A@mail.gmail.com>
	<CAKFQuwaGO-pmBVc2Vk9vwmbkhNpxHeZM77=oCtG+Duoc-G58cg@mail.gmail.com>
	<[email protected]>

On Thu, Aug 7, 2025 at 4:21 PM Tom Lane <[email protected]> wrote:
> 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.

Hi Tom.

Indeed it was. I shared my psql session showing that.

> 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.

That's better than nothing. And I get it's likely complex.

But still, arg names are not part of the signature.
So they should be checked after the fact.

In my case, the SCHEMA eas explicit, so no search_path.
With the ::name cast, the signature was an exact match.
And there are no overloads at all.

So it's possibly the "worse case" for saying the proc does NOT exist...
It's like the code should do a LEFT JOIN instead of a JOIN on arg names :).

--DD

view thread (10+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: CALL and named parameters
  In-Reply-To: <CAFCRh-_zu2hQpACVQaxGiuCFe5FWnEWQCb6TRCa-zfC539mF0g@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox