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 1tXdyW-00BesO-Vf for pgsql-admin@arkaria.postgresql.org; Tue, 14 Jan 2025 10:16:45 +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 1tXdyV-00H0BF-Hg for pgsql-admin@arkaria.postgresql.org; Tue, 14 Jan 2025 10:16:44 +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 1tXdyV-00H0B5-1C for pgsql-admin@lists.postgresql.org; Tue, 14 Jan 2025 10:16:43 +0000 Received: from mail-yb1-xb31.google.com ([2607:f8b0:4864:20::b31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tXdyU-000KyT-0Z for pgsql-admin@postgresql.org; Tue, 14 Jan 2025 10:16:42 +0000 Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-e3978c00a5aso8178328276.1 for ; Tue, 14 Jan 2025 02:16:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736849800; x=1737454600; 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=lkHADOrDPCoUZmXvn3wVgxV4u7lyoVlG/TXrDyPu1SQ=; b=VYEwdgTQvjnjx/EYguCPNkLAYYuFcnIjmWysH7nfb8l76UBNv4HrodV15nOcTRxfie 25Hzl9HAUO7SO2mCrgDF3S4CMpYtXbYlPaifTfnRN9KRbHgW66hygDRIVus/MZxU9zJx iJH+6fW4GZ0ud4EVFDFegTWVZ4x8IGV7yf/hKtuet+VclDjB2ZhOQq2OR2sbGvue/uoX UexqvSWkRDjXd4i8AuRZUtMbbm/VyjDSIXxXAhGIdK6jDxA3tSFH0pqWA2aUhTrEHXOj HhcGUKn0SIeNhsQFy+iTM4igXVymqWikY5Ygj1BDYhxcjOHWGO5Bpz1SpKCjbCGMWU6j PLXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736849800; x=1737454600; 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=lkHADOrDPCoUZmXvn3wVgxV4u7lyoVlG/TXrDyPu1SQ=; b=oWcbPUIyr9hWOmkTOGmI+5UCc3nqGmMu/jbyklDDqttWQXPhsfR6z32v4OSVcd3Quu D6EtwGeYlaTYNR2X7D0K9cC5mHLB7rQdc5CGMRlmGnVYUV1560ERvZdCizMl4mlm3W5a MetLrSRhNcVR0fukbikom5lSmDIfTi7QDsQUvVMowD56V/H/RR6FZU9AU9oKyZBJSaly 8uHYPPuKIPhQF1RTSlPql4Tjx6z/m/Wauv9U64gyXW/GHdh00LkaEZTYMWzXA/M8R5Bw 99ktAbA1NG6wL+S1GnJtQCa1W7R8xIa04SjAHVKLRoceiP9a+tqTt9MGzIZcPFP0mgFQ 3zlA== X-Forwarded-Encrypted: i=1; AJvYcCUQszYuNaZNJNoNiBFr3ELJ7xSLIn43MVs8hEi05Bbs3d5YRgrbEzj9WZqpeBHtpWZNe7avFHNLoTyrfQ==@postgresql.org X-Gm-Message-State: AOJu0Yz56nZcp7zqVLOTEMbeQLEqxseT/hv3l4ueXgIDZgQR0OD8Kqil anzzFxTGFFqpVht0Rz9hXI6SIBThVtppWHnVEgTYuRIxubeDuZx4AsqLHpcSFa8phWlSlUrsnU/ A4HDSP23E9ztUoKGQvXyw8d/S8rg= X-Gm-Gg: ASbGnct/LC5jfHzJelEfVl/j6SaQAxyrgQHoYXmB4jgdVtZNquIM2qzWlWeASo+Cs1R /gwXESoiF72LwUFC7n2MhYKdDHvZgEj8w4BYKNg== X-Google-Smtp-Source: AGHT+IGMcAGpenhQ/Ccx7aOqBsnVpib+HE8XglLrwZMCqyUIsdaZaUox0mYxDXQhfgRCTnEqyMZAl6jBlp0QrYBHaLc= X-Received: by 2002:a05:690c:b98:b0:6ef:5ab8:2c53 with SMTP id 00721157ae682-6f5312372e9mr193545177b3.19.1736849800435; Tue, 14 Jan 2025 02:16:40 -0800 (PST) MIME-Version: 1.0 References: <1334421.1736193470@sss.pgh.pa.us> In-Reply-To: From: kaido vaikla Date: Tue, 14 Jan 2025 12:16:29 +0200 X-Gm-Features: AbW1kvbzMZXEFxBHfm7mAF6VGVlGVv6u3LW3H8__Cn7kTporzG6jlwLJD6iCHoI Message-ID: Subject: Re: How to debug extension update To: Zaid Shabbir Cc: Tom Lane , pgsql-admin Content-Type: multipart/alternative; boundary="000000000000622064062ba7db5d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000622064062ba7db5d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 1) requires =3D 'postgis' $ cat postgis_topology.control # postgis topology extension comment =3D 'PostGIS topology spatial types and functions' default_version =3D '3.3.6' relocatable =3D false schema =3D topology requires =3D postgis So i changed it requires =3D postgis -> requires =3D 'postgis' but no help. 2) about missing access privileges I checked different databases with \dT+ *.* data types "Access privileges" is everywhere empty. As my subject is, is it there a way somehow debug "alter extension update" statement to figure out what is going on behind this? br Kaido On Mon, 6 Jan 2025 at 22:05, Zaid Shabbir wrote: > 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 wrot= e: > >> 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 >> >> >> --000000000000622064062ba7db5d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
1)= requires =3D 'postgis'

$ cat postgis_topology.control
# postgis topo= logy extension
comment =3D 'PostGIS topology spatial types and funct= ions'
default_version =3D '3.3.6'
relocatable =3D falseschema =3D topology
requires =3D postgis

So i changed it=C2=A0<= br>requires =3D postgis ->= =C2=A0 requires =3D 'postgis'=
but no help.

2)=C2=A0about missing acce= ss privileges
I checked different databases with=C2=A0
\dT+ *.*
data types=C2=A0"Access privileges" is=C2=A0everywhere=C2=A0emp= ty.

As my subject is, is it there a way somehow debug "alter ex= tension update" statement=C2=A0to figure out what is going on behind t= his?

br
Kaido




On Mon, 6 Jan 2025 at 22:05, Za= id Shabbir <z= aidshabbir@gmail.com> wrote:
Hello,

I am also ge= tting 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" d= oes 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" d= oes not exist

postgres=3D# SELECT current_schema();

=C2=A0current_schema=C2=A0<= /span>

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

=C2=A0postgis

(1 row)


Regards,
Zaid


<= div>

On Tue, Jan 7, 2025 at 12:58=E2=80=AFAM Tom Lane <tgl@sss.pgh.pa.us> = wrote:
kaido vai= kla <kaido.v= aikla@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


--000000000000622064062ba7db5d--