[postgis-tickets] [PostGIS] #2485: [raster]: raster constraints prevent raster data from restoring

[PostGIS]

#2485: [raster]: raster constraints prevent raster data from restoring
----------------------+-----------------------------------------------------
 Reporter:  rdunklau  |       Owner:  dustymugs    
     Type:  defect    |      Status:  new          
 Priority:  critical  |   Milestone:  PostGIS 2.0.5
Component:  raster    |     Version:  trunk        
 Keywords:            |  
----------------------+-----------------------------------------------------

Comment(by robe):

 I just thought of another possibly brilliant or really stupid work around
 for this issue.

 We explicitly add search_path to these functions something like


 {{{
 ALTER FUNCTION _raster_constraint_pixel_types(raster)
   SET search_path=pg_catalog,public,postgis;

 }}}


 I think we might even be able to do this in the code base too with the
 assumption that most people install postgis in public or postgis schema.
 I recalled a while back that PostgreSQL would complain if you added a non-
 existent search path, but lately I don't seem to be noticing that problem.


 rdunklau - if you are listing, the trick is to install postgis as usual
 with

 CREATE EXTENSION .. and then add these search paths to these select
 functions, and then restore your data.  This is the trick I've used in the
 past to allow be to get away with using ST_Transform in an index and have
 my indexes come back during restore.  Which had similar issues (by setting
 search_path of ST_Transform function)

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2485#comment:29>
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.