Re: How to debug extension update
| От | Zaid Shabbir |
|---|---|
| Тема | Re: How to debug extension update |
| Дата | |
| Msg-id | CABCJe_Wu8K0jteiN-JM_Grhy8fL1WKeH7UrWk_1TpOwumoR-nQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: How to debug extension update (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-admin |
Hello,
I am also getting the same error without the upgrade scenario.
postgres=# CREATE EXTENSION postgis SCHEMA postgis;
CREATE EXTENSION
postgres=# CREATE EXTENSION postgis_topology SCHEMA topology;
ERROR: type "geometry" does not exist
postgres=# show search_path ;
search_path
---------------------------
postgis, topology, public
(1 row)
postgres=# CREATE EXTENSION postgis_topology;
ERROR: type "geometry" does not exist
postgres=# SELECT current_schema();
current_schema
----------------
postgis
(1 row)
Regards,
Zaid
On Tue, Jan 7, 2025 at 12:58 AM 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 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
В списке pgsql-admin по дате отправления: