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 1tUtEa-003apF-Td for pgsql-admin@arkaria.postgresql.org; Mon, 06 Jan 2025 19:57:57 +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 1tUtEY-00Byib-B6 for pgsql-admin@arkaria.postgresql.org; Mon, 06 Jan 2025 19:57:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tUtEX-00ByiB-W0 for pgsql-admin@lists.postgresql.org; Mon, 06 Jan 2025 19:57:53 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tUtEV-000ChR-0F for pgsql-admin@postgresql.org; Mon, 06 Jan 2025 19:57:52 +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 506JvoU91334422; Mon, 6 Jan 2025 14:57:50 -0500 From: Tom Lane To: kaido vaikla cc: pgsql-admin Subject: Re: How to debug extension update In-reply-to: References: Comments: In-reply-to kaido vaikla message dated "Mon, 06 Jan 2025 18:49:16 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1334420.1736193470.1@sss.pgh.pa.us> Date: Mon, 06 Jan 2025 14:57:50 -0500 Message-ID: <1334421.1736193470@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk kaido vaikla writes: > Why update can't find an extension, while i can describe it and search_path > seems to be correct? Extension scripts are not run with the session's prevailing search_path, but with a search path built from the extension's dependencies. In this case, schema postgis would be included in that path only if extension postgis_topology specifies requires = 'postgis' in its postgis_topology.control file. It kinda sounds like that might be missing? If it's present, then Ron's thought about missing access privileges for the postgis schema might be the answer. regards, tom lane