[Qgis-user] DB Manager geometry problems

[Chris Buckmaster]

Thanks Karl-Magnus – for some reason I thought they already had privileges but they didn’t, thanks again!

Chris

From: Karl-Magnus Jönsson [mailto:Karl-Magnus.Jonsson at kristianstad.se]
Sent: 21 March 2016 06:27
To: Chris Buckmaster; qgis-user at lists.osgeo.org
Subject: SV: DB Manager geometry problems

Hi Chris

Appears that the user can’t access the view geometry_columns in the public schema. The information is accessed from there. Grant select privileges.

Karl-Magnus Jönsson │GIS-utvecklare
Miljö- och samhällsbyggnadsförvaltningen, avd. Geografisk information
Kristianstads kommun
291 80 Kristianstad
Besöksadress: Västra Storgatan 12
Tel 044-13 54 16 │ Mobil: 0733-13 54 16 │karl-magnus.jonsson at kristianstad.se
www.kristianstad.se<http://www.kristianstad.se/>

Från: Qgis-user [mailto:qgis-user-bounces at lists.osgeo.org] För Chris Buckmaster
Skickat: den 18 mars 2016 16:34
Till: qgis-user at lists.osgeo.org
Ämne: [Qgis-user] DB Manager geometry problems

Hi

I have several datasets loaded into PostGIS 2.0 with the owner as ‘superuser’ that has full permissions. I have then assigned select permissions to some other users, but I am not sure if they completely have the access they require as the DB Manager doesn’t show the spatial reference, and it says there is no entry in geometry_columns (attached are two screenshots which show what I get).

For my superuser connection, the geometry symbol is next to the layer name and it has all of the geometry information in the window, but for one of my select only users it does not show – do I need to give my select only users permission to access other tables in PostGIS? I have noticed that for larger datasets it takes quite a bit longer for the datasets to be loaded into PostGIS as well which leads me to believe that perhaps they are not accessing the spatial indexes or something?

Thanks, Chris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20160321/3deff379/attachment.html>