[postgis-tickets] [PostGIS] #2821: Raster import fails if "raster_columns" is not readable by the user

[PostGIS]

#2821: Raster import fails if "raster_columns" is not readable by the user
---------------------+------------------------------------------------------
 Reporter:  strk     |       Owner:  dustymugs    
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.1.4
Component:  postgis  |     Version:  2.1.x        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by robe):

 strk -- which version of PostGIS are you using? Can you retest with the
 latest.

 I'm really confused why this is even an issue and am tempeted to close as
 invalid.  We already have raster_columns as publically readable.  See our
 script at bottom of rtpostgis.sql.in


 {{{
 GRANT SELECT ON TABLE raster_columns TO public;
 GRANT SELECT ON TABLE raster_overviews TO public;
 }}}

 and in my db it is publically readable.


 The reason we made it publically readable (same reason we have
 geography_columns and geometry_columns) readable is because all the views
 already check if users have rights to said tables.  So if they don't they
 wouldn't show up anyway in there query.

 Presumably anyone creating a table via import would have rights to see the
 table and its constraints. You definitely should not be getting a
 permission denied and if you are witht eh latest 2.1.3, something else is
 wrong.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2821#comment:5>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.