Feedback-ID: i76984098:Fastmail
Message-ID: <94f7cf0f-ee15-4e6a-b5eb-f70bbbaa520a@aklaver.com>
Date: Wed, 6 Aug 2025 11:10:55 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: CALL and named parameters
To: Dominique Devienne <ddevienne@gmail.com>,
 pgsql-general@lists.postgresql.org
References: <CAFCRh-_iLoUtMAtyunw_-O6sgpWo04sOmB38MUVNpuQVSkL_0Q@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAFCRh-_iLoUtMAtyunw_-O6sgpWo04sOmB38MUVNpuQVSkL_0Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/94f7cf0f-ee15-4e6a-b5eb-f70bbbaa520a%40aklaver.com>
Precedence: bulk

On 8/6/25 10:48, Dominique Devienne wrote:
> (sorry, this is a rant...).
> 
> Was getting an error calling a procedure
> 
> ERROR:  procedure ... does not exist
> HINT:  No procedure matches the given name and argument types. You
> might need to add explicit type casts.
> 
> I verify USAGE on the SCHEMA of the proc. OK.
> I verify EXECUTE on the FUNCTION. OK.
> I verify the names of the parameters, in my CALL with named arguments. OK.
> 
> Turns out, thanks to ChatGPT for clueing me in, CALL does NOT support
> named parameters. And it's about the least helpful error message
> PostgreSQL could have provided IMO. I'd expect something much better
> in this specific case, FWIW.

I am not following as:

CREATE OR REPLACE PROCEDURE public.call_test(IN a integer, IN b integer)
  LANGUAGE plpgsql
AS $procedure$
BEGIN
     RAISE NOTICE 'c = %', a + b;
END;
$procedure$


call call_test (a=>1, b=>2);
NOTICE:  c = 3
CALL


You will need to provide more information on your specific case.

> 
> That's two unhelpful error messages in a short time :).
> 
> Thanks, and again sorry for the rant. Wasted time on this. --DD
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com