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 1tUtLc-003bom-LF for pgsql-admin@arkaria.postgresql.org; Mon, 06 Jan 2025 20:05:13 +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 1tUtLc-00C7R8-3d for pgsql-admin@arkaria.postgresql.org; Mon, 06 Jan 2025 20:05:11 +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 1tUtLb-00C7Qo-Lk for pgsql-admin@lists.postgresql.org; Mon, 06 Jan 2025 20:05:11 +0000 Received: from mail-ed1-x533.google.com ([2a00:1450:4864:20::533]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tUtLY-000DTn-0s for pgsql-admin@postgresql.org; Mon, 06 Jan 2025 20:05:10 +0000 Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-5d84179ef26so1727847a12.3 for ; Mon, 06 Jan 2025 12:05:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736193908; x=1736798708; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pDKK8qYq+UfF6jgP2M6Rc8CMiThjT1DQkIIJ5c+6L+A=; b=kYnbqRK6+s1lkgE8qHkPlFzVkbkidjSrYLv7e6+HAw7jkRJRjYWQrWPJiSvj3pZXnu llt3M6ZaLSHd1LMuQlfLoRF8EqaaKZzZ2DjErTIsiuQzJc2UIg/2xtJKBhdl2Xcy5dk1 Pk5I5GMrZ1WCwy78otCzkZMSN3TPlxcbjkBNZ32JLebyAAUN48O+KmNVkaxjGO1OOFnI lW7qBmZlGl0Yk95PENDh4itICas8S9Wn4PHaOG30GDQblsAUl6t4Jj4HORVHg50SAEbI KA0KgLU5Xs2mJ6/UcGelwP4N89XvT7AulBOGgytDL3euFIysHjnx4PXjVfST2vR6kQ2B ochQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736193908; x=1736798708; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pDKK8qYq+UfF6jgP2M6Rc8CMiThjT1DQkIIJ5c+6L+A=; b=hMxd1HnUBWfYacp4ie2q9zdyRyumNlBL5EcQw+9Luuo8bZKGWUV7pOa2kgr9rbmDdq yyK65KTUQYdozF8bn/5aetoHtDeHQvF2e6KC8AuhbwiYVC4OLydi8ZL4ofq4PKuzyOvN 4yW9RxzaDLpSsQROvzH/z4Uqh3t8L2pSfBxeQ9KqqKxIYSTmp/oxEbDmu41nsdt1NiZO 4H79vXvCLsAt8ddOtXyNmy3PLlGIA5erA7E467fWZjY98bXpfAmepEC4FMnL09g4e5ru H37hrt6qBwcDoh8JGRU7EaENfVYOjtB6P5BKqaJM+Xpihf9UIsQpkUfRyrFXYJysiyF1 L7gw== X-Gm-Message-State: AOJu0YzxxnzekNrKys2Wtb92fvWbU4pqi7/bkNWmAKz968scaiq3Fmdx OgKe8Gx+HKoZLtm5buLVgtks7x17h8dINVuNwKI93iscdxKbKdip/MgAKxsDHkvSvyFZ4gUpeXN MfkJguX61oh+x9wPVot1mrqJBhJQ= X-Gm-Gg: ASbGncsaN9U76anrNHnTmugrDWBYbgQqNuWGQ+mIVMyBY+QDO3LsaeL6UirhMAyZNLD sWM+fsMCn8g6eoPZkL2r1406UiGgg08Hyr9wXhDoqrm0x1Eok12Ly8l+tW0oBP00acQglIg== X-Google-Smtp-Source: AGHT+IEp9b0KALFlMOfDtEcT2KJZIZt1OSNC8Bk9gX/0wigGVL08NWuGYs0js99pXIL0fMEeJDHgRjrYEaWSsU62GMc= X-Received: by 2002:a05:6402:13d6:b0:5d3:e4eb:8d1f with SMTP id 4fb4d7f45d1cf-5d81dd906dbmr50379388a12.12.1736193907871; Mon, 06 Jan 2025 12:05:07 -0800 (PST) MIME-Version: 1.0 References: <1334421.1736193470@sss.pgh.pa.us> In-Reply-To: <1334421.1736193470@sss.pgh.pa.us> From: Zaid Shabbir Date: Tue, 7 Jan 2025 01:04:56 +0500 Message-ID: Subject: Re: How to debug extension update To: Tom Lane , kaido.vaikla@gmail.com Cc: pgsql-admin Content-Type: multipart/alternative; boundary="00000000000023d677062b0f25fe" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000023d677062b0f25fe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, I am also getting the same error without the upgrade scenario. postgres=3D# CREATE EXTENSION postgis SCHEMA postgis; CREATE EXTENSION postgres=3D# CREATE EXTENSION postgis_topology SCHEMA topology; ERROR: type "geometry" does not exist postgres=3D# show search_path ; search_path --------------------------- postgis, topology, public (1 row) postgres=3D# CREATE EXTENSION postgis_topology; ERROR: type "geometry" does not exist postgres=3D# SELECT current_schema(); current_schema ---------------- postgis (1 row) Regards, Zaid On Tue, Jan 7, 2025 at 12:58=E2=80=AFAM Tom Lane wrote: > 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 =3D '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 > > > --00000000000023d677062b0f25fe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

I am also getting the same error= without the upgrade scenario.

postgres=3D# CREATE EXTENSION postgis SCHEMA postgis;

CREATE EXTENSION

postgres=3D# CREATE EXTENSION postgis_topology SCHEMA= topology;

ERROR:=C2= =A0 type "geometry" does not exist

postgres=3D# show search_path ;

=C2=A0 = =C2=A0 =C2=A0 =C2=A0 search_path =C2=A0 =C2=A0 =C2=A0 =C2=A0

---------------------------

=C2=A0postgis, topology, public

(1 row)

postgres=3D# CREATE EXTENSION postgis_topology;

ERROR:=C2= =A0 type "geometry" does not exist

postgres=3D# SELECT current_schema();

=C2=A0current_schema=C2=A0=

----------------

=C2=A0postgis

(1 row)


Regards,
Zaid




On Tue, Jan 7, 2025 at 12:58=E2=80=AFAM Tom Lane <tgl@sss.pgh.pa.us> wrote:
kaido vaikla <kaido.vaikla@gmail.com> writes:
> Why update can't find an extension, while i can describe it and se= arch_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.=C2=A0 In this case, schema postgis would be included
in that path only if extension postgis_topology specifies

=C2=A0 =C2=A0 =C2=A0requires =3D 'postgis'

in its postgis_topology.control file.=C2=A0 It kinda sounds like that
might be missing?=C2=A0 If it's present, then Ron's thought about missing access privileges for the postgis schema might be the
answer.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane


--00000000000023d677062b0f25fe--