[postgis-devel] [PostGIS] #1746: Moving postgis extension to another schema leaves things behind

[PostGIS]

#1746: Moving postgis extension to another schema leaves things behind
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.0.1
Component:  postgis  |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------
 I haven't bothered ticketing this because a long time ago it wasn't
 possible when I first tried it.

 If I start with a beta install and upgrade to say rc2 and then I move my
 postgis extension to a new schema.  There are two functions left behind.


 {{{
 st_dump(postgis.geom), st_isvaliddetail(postgis.geometry)
 }}}

 Steps to create.


 {{{
 -- install beta2 or--
  CREATE EXTENSION postgis ;

 -- install rc1 or rc2 --
 ALTER EXTENSION postgis UPDATE TO "2.0.0rc2";
 CREATE SCHEMA postgis;
 ALTER EXTENSION postgis SET SCHEMA postgis;

 }}}

 When I upgrade one that I've been upgrading for a while I actually have 6
 functions left behind in public.

 st_dump, st_intersection(postgis.raster....) (4 permutations of this),
 st_isvaliddetail(postgis.geometry).

 These might be signature changes we didn't drop so may be a sign of us not
 populating the drop scripts for these.

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