It seems that qgis automatically searches after postgis in postgresql's public schema rather than in its search_path parameter. If postgis is installed in another schema (something you may want to do as postgresql policy is try to not use the public schema anymore), qgis can no longer understand table geometries, can't find any functions ...
Steps to reproduce the issue
create a new database testdb
create a schema named extensions
install postgis with :
CREATE EXTENSION postgis SCHEMA extensions;
ALTER DATABASE testdb SET search_path = public,extensions;
open qgis and try to create a connection toward this database
Versions
3.38
Supported QGIS version
[X] I'm running a supported QGIS version according to the roadmap.
I cannot reproduce locally, I followed your instructions but QGIS is able to create and to see all spatial tables in both extensions and public schema.
What is the bug or the crash?
It seems that qgis automatically searches after postgis in postgresql's public schema rather than in its
search_path
parameter. If postgis is installed in another schema (something you may want to do as postgresql policy is try to not use the public schema anymore), qgis can no longer understand table geometries, can't find any functions ...Steps to reproduce the issue
Versions
3.38
Supported QGIS version
New profile
Additional context
No response