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 1m1qmO-0002Nq-CD for pgsql-sql@arkaria.postgresql.org; Fri, 09 Jul 2021 13:42:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m1qmN-0007ew-B5 for pgsql-sql@arkaria.postgresql.org; Fri, 09 Jul 2021 13:42:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m1qmN-0007eo-48 for pgsql-sql@lists.postgresql.org; Fri, 09 Jul 2021 13:42:55 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m1qmK-0002RT-R6 for pgsql-sql@lists.postgresql.org; Fri, 09 Jul 2021 13:42:54 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 169Dgjoi2091964; Fri, 9 Jul 2021 09:42:45 -0400 From: Tom Lane To: Prajakta Chinchole cc: "pgsql-sql@lists.postgresql.org" Subject: Re: Support for PostgreSQL stored procedure through ITX. In-reply-to: References: Comments: In-reply-to Prajakta Chinchole message dated "Fri, 09 Jul 2021 05:53:46 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2091962.1625838165.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 09 Jul 2021 09:42:45 -0400 Message-ID: <2091963.1625838165@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Prajakta Chinchole writes: > We are trying to execute a PostgreSQL stored procedure through ITX. We a= re using ODBC driver that was provided with PostgreSQL. We observed that s= qlExecDirect() failed for stored procedure with below error : > DIAG [42809] ERROR: public.transfer(integer, integer) is = a procedure; > Error while executing the query (1) You might have more luck asking about this on the pgsql-odbc mailing list. Also, make sure you're using an up-to-date release of the ODBC driver. regards, tom lane