Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pHSB3-0002Z5-VH for pgsql-general@arkaria.postgresql.org; Mon, 16 Jan 2023 16:17:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pHSB2-0000hH-O8 for pgsql-general@arkaria.postgresql.org; Mon, 16 Jan 2023 16:17:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pHSB1-0000fh-I6 for pgsql-general@lists.postgresql.org; Mon, 16 Jan 2023 16:17:40 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pHSAu-0000x7-Cm for pgsql-general@lists.postgresql.org; Mon, 16 Jan 2023 16:17:38 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 282265C0144; Mon, 16 Jan 2023 11:17:31 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 16 Jan 2023 11:17:31 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1673885851; x= 1673972251; bh=2h8/FeZdBsSHDVgIaGLdzZTegIiQ0CGk0lpe6H+TgYo=; b=N 916OeiHlzSulpLBLpTqHrpEuaPJTqjqWqcY7nMWf/zMquvWzEEkc5HcXdCHccIhJ /XSMwp+wZ+U1h1Q1nXVJPysNN3teuLPzmDFDh43pQKJJNNqlKxGq0NkszLxZ3t9b rFaqtw32PZa3MFSbObbH/D+tvr+bnFRu0+EZ/DqLpj7UP7/DgBrUPj78Rel2cKLf HleZFTj+NmpiJEY5icx1q91/MhnQQevFd3HGE1UsMO9uAh+db8udJnNcn25+F3J9 3+9Qk1Cr+uP7tZ5YJYDYPutbC+6DwhHGGhMjKQ6lcGA22xVeOYlJEn+nzChYTRKa dmFMc2lgL+Y1fLmsgHFew== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1673885851; x=1673972251; bh=2 h8/FeZdBsSHDVgIaGLdzZTegIiQ0CGk0lpe6H+TgYo=; b=IgCqdsUoqYZ4Xvdl2 tk+WiNKJE7hTqsEYKEmo3/DeQpL+ZInAb9OUMtbg6ryEuoSR+NHQlYS7efJGKR4v G6bvCkFk3iS+l4oQWFz7BjNYTnDKgPDi5z3esE+6yvDPoGbe9/R4ljn8cE/bSHbq kFM6+jzFR97n8jrccr29e+Xw2IyhyZ/pFg1p1OxOIx64HD8AckHOM75koOVWA7qx UdHS3lR0BqHIDzJiWEbkrSCDmBIB4hdhJQzamt/PR2MX3Jzw+WZmSnMr7WZNqVIg wR47bRNdEaJyVFUlHbhjlW9PJO01F8M0bKylo2FKEyhABJvei3BAcyiMitSVp0FO RTbTg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddtgedgkeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtfeejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhk lhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepudfgueelge evfffhgeeljeehhfettdegieelgefgheefffefveegjedtueetffdtnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvh gvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 16 Jan 2023 11:17:30 -0500 (EST) Message-ID: <2418e79e-a2ca-6fa5-205b-8b39dbf9ffec@aklaver.com> Date: Mon, 16 Jan 2023 08:17:29 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: No function matches the given name and argument types. To: arons , pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/16/23 08:04, arons wrote: > Dear All, > I'm facing a general problem and I'm looking the best, fastest, way how > to identify the problem and solve it. > > As example assume we have a function like that: > > CREATE OR REPLACE FUNCTION testBinding01 ( > > p_in01 bigint, > > p_in02 bigint, > > p_in03 bigint, > > p_in04 bigint, > > p_in05 bigint, > > p_in06 bigint, > > p_text7 text > > ) RETURNS text > > LANGUAGE sql > > AS $$ > > select 'ciao'; > > $$; > > > > I can call the function in some of the variant below: > > select testBinding01(1,2,3,4,5,6,7); > > select testBinding01(p_in01 => 1,p_in02 => 2,p_in03 => 3,p_in04 => > 4,p_in05 => 5,p_in06 => 6,p_text7 => 7); > > select testBinding01(p_in01 => 1,p_in02 => 2,p_in03 => 3,p_in04 => > 4,p_in05 => 5,p_in06 => 6,p_text9 => 'some txt'); > > > All of the above, produce the error: > > *No function matches the given name and argument types.* In psql what does: \df test* return for the function name. I'm going to guess it might be testBinding01, in other words mixed case. Have you tried?: select "testBinding01"(1,2,3,4,5,6,7); > * > * > * > * > * > * > My question is: how is the best way  to identify the problem? > > Is a parameter name? is a parameter type? is the function name? > > An especially in case is a parameter type how is the easy way to > identify which parameter is causing the problem? > > In case a function has a lot of parameters (and in even worst case has > some overloading) going trough all parameters to check its type/name > costs a lot of time. > > > Thanks for any help > > Renzo > > > -- Adrian Klaver adrian.klaver@aklaver.com