[postgis-tickets] [PostGIS] #3012: Calling ST_AsLatLonText in matviews causes unrestorable pg_dump

[PostGIS]

#3012: Calling  ST_AsLatLonText  in matviews causes unrestorable pg_dump
--------------------------+-------------------------------------------------
 Reporter:  jeffcasavant  |       Owner:  robe         
     Type:  defect        |      Status:  new          
 Priority:  medium        |   Milestone:  PostGIS 2.2.0
Component:  postgis       |     Version:  2.1.x        
 Keywords:                |  
--------------------------+-------------------------------------------------

Comment(by robe):

 By your assessment was not quite right, I meant to say that the title was
 a little misleading. This is an issue only with PostGIS functions that
 call other PostGIS functions, and not with all PostGIS functions as the
 original title had suggested.  Sadly we do have a lot of these it seems
 and as people start using materialized views more and more, it will become
 more of an issue.

 Luckily it's not an issue with regular views since those don't try to run
 the functions in the view.  One thing I haven't tried is defining a
 materialize view with NO DATA.  I'm not sure if pg_dump maintains that
 setting.  I'm guessing it does.  That said -- another work around would be
 to do:



 {{{
 CREATE MATERIALIZED VIEW vw_mat_postgis
     AS  SELECT ....

     WITH NO DATA;
 }}}

 and then after restore run a

 {{{

 REFRESH MATERIALIZED VIEW vw_mat_postgis;
 }}}

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