[postgis-tickets] [PostGIS] #2905: Ensure that raster_columns is always readable by public unless explicitly made unreadable

[PostGIS]

#2905: Ensure that raster_columns is always readable by public unless explicitly
made unreadable
--------------------+-------------------------------------------------------
 Reporter:  robe    |       Owner:  dustymugs    
     Type:  defect  |      Status:  new          
 Priority:  medium  |   Milestone:  PostGIS 2.1.4
Component:  raster  |     Version:  2.1.x        
 Keywords:          |  
--------------------+-------------------------------------------------------
 This is related to #2821.  Some how strk got himself into a state where
 raster_columns is not readable by all users of a db, and thus raster
 import failed.

 We currently have raster_columns as publically readable in the
 rtpostgis.sql.in

 via

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

 Looking at my views, these lines DO show on permissions of these views.
 If a database were to be restored then CREATE EXTENSION would run which
 would reapply these permissions. Said permissions should also be included
 in upgrade.  Perhaps they are not -- we need to confirm they are.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2905>
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.