Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfNUT-00HHwF-U1 for pgsql-general@arkaria.postgresql.org; Wed, 28 Feb 2024 17:13:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rfNUS-00Cwyi-GG for pgsql-general@arkaria.postgresql.org; Wed, 28 Feb 2024 17:13:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfNUS-00CwyZ-5t for pgsql-general@lists.postgresql.org; Wed, 28 Feb 2024 17:13:08 +0000 Received: from wfout3-smtp.messagingengine.com ([64.147.123.146]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfNUQ-001p0z-5n for pgsql-general@lists.postgresql.org; Wed, 28 Feb 2024 17:13:08 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.west.internal (Postfix) with ESMTP id 4544C1C00086; Wed, 28 Feb 2024 12:13:02 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 28 Feb 2024 12:13:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1709140381; x=1709226781; bh=qjEvCPmPLokqTU84CYGlB8Nzs/niKvEj1JoWpLRzL9w=; b= d0DVG4JRf3MRHjYlPs8pmE76aw0ZL9+YVAaSKCgieHDSNkzNbLZf3DXtJwOQxxMY FIwDXM9aeJZBINWY914X5+lwDdjxmlUZDIF9mgiV+5bAZHDWZBbEqahgaIe2WppP GzhyTGnKie7FLES/BKIGndIXpjv2pmwgghADlXNQm/ch2L1Ki4QdzfZzAN3mlGBg t8Oc1LrQ3k1x8SkpqUjT1yrtJ6abvUJAT8tWwBUCOMXhR+Xq1w8y9rLgzvMQvTb6 yPVfm/Ka5k7aWxF1//a4Hy/yF4GC3OUmeEyEcKnf9appT2w7o8v1rI3eSL6++Aiw +gjzQOQc5qOpwiP1U80fOA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1709140381; x= 1709226781; bh=qjEvCPmPLokqTU84CYGlB8Nzs/niKvEj1JoWpLRzL9w=; b=d BLLhhSqCnLZfzElJHaUljpiG60vwt5hHAQVMvatPKHH1WV6euxDzTZVKaavwlQP2 BvlR4Olrz9/3M47YWH8XmvU3i5q+zlUamoM1MADtsllabNj1vcfgFqmxin3f/XCt VdsMCajfptWgXbSOxAsyhOVX+8gTS+u43sRblVh98oeiU0JQbhzKAwqyvxCbPn2X +Gl3jZ24xuygGHEr0A5GuqA0gS8F/p1Gxygr7BfNya+D3zSJkiXCZL6f1Nu2nxHW QXIlFgFBLKY9PriFuiIurRp0MbdJlNavFwlPKNc+brAMxfncrJVfYi0x9r33RuQS gQD8RtYYSgavcB0EX2wwg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrgeejgdelfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeefgeefieeutdfggfetgefgheekjeehteeileeigfet ieekjedvieeviefgheevtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 28 Feb 2024 12:13:00 -0500 (EST) Message-ID: <5a9477e8-d1aa-435e-a547-19eb041cc643@aklaver.com> Date: Wed, 28 Feb 2024 09:13:00 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Need Assistance: Command to display procedures does not work Content-Language: en-US To: Sasmit Utkarsh , Rob Sargent Cc: pgsql-general@lists.postgresql.org References: 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 2/28/24 09:08, Sasmit Utkarsh wrote: > Thanks Rob > > So which one could I rely on for better information? probably, results > shown by PgAdmin4 right? As  I get the below when I try to drop > procedure through psql cmd and i see the procedure getting fetched from > the query > > shc_data=> SELECT proname AS function_name,proacl AS privileges FROM > pg_proc WHERE proname in > ('sql_insert_data_procedure','sql_select_data_procedure','sql_select_size_procedure','sql_update_data_procedure'); >        function_name       | privileges > ---------------------------+------------ >  sql_select_size_procedure | >  sql_select_data_procedure | > *sql_insert_data_procedure* | >  sql_update_data_procedure | > (4 rows) > > shc_data=> DROP PROCEDURE *sql_insert_data_procedure*; > ERROR:  could not find a procedure named "sql_insert_data_procedure" > shc_data=> We've been down this road before, it is a search_path issue. In psql do: SHOW search_path; then do: \df *.sql_insert_data_procedure Then see if the schema shown in the second command is in the search_path returned by the first command. > > Regards, > Sasmit Utkarsh > +91-7674022625 > -- Adrian Klaver adrian.klaver@aklaver.com