This I suppose could be a permission issue or search path one.
Are you using the same account in QGIS to connect as you are in pgAdmin? Are you connecting from QGIS PostGIS layers or via QGIS DBManager menu option? If you haven’t tried DBManager, I would try that to see what tables you are able to see. That should give you a clue if it’s a permission issue. From: postgis-users [mailto:[email protected]] On Behalf Of Simon SPDBA Greener Sent: Thursday, September 29, 2022 2:03 AM To: [email protected] Subject: Re: [postgis-users] No extension Regina, Thanks for the reply. > What does > SELECT * FROM geometry_columns; > Return. I’m guessing maybe QGIS is complaining about lack of spatial tables. It returns a data grid showing all the spatial layers. > Looked like your PostgreSQL 13 is running on 5432, you could just disable it. > I assume it’s maybe still running in services? The strange thing was that it had been uninstalled. I removed the rogue connection in PgAdmin 4 and it fixed the problem. In my new instance I created a database for each of the backup databases, execute "create extension postgis" for all of them, then restored the original data from the backups successfully. I am still getting this in qGIS logs... 2022-09-29T14:38:36 WARNING No PostGIS support in the database. 2022-09-29T14:38:36 WARNING Database connection was successful, but the accessible tables could not be determined. regards Simon -- Simon Greener 39 Cliff View Drive, Allens Rivulet, 7150, Tasmania, Australia (m) +61 418 396 391 (w) www.spdba.com.au <http://www.spdba.com.au> (m) [email protected] <mailto:[email protected]>
_______________________________________________ postgis-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/postgis-users
