[postgis-devel] [PostGIS] #202: upgrade issues

[PostGIS]

#202: upgrade issues
----------------------+-----------------------------------------------------
  Reporter:  robe     |       Owner:  robe         
      Type:  defect   |      Status:  assigned     
  Priority:  medium   |   Milestone:  postgis 1.4.1
 Component:  postgis  |     Version:  trunk        
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------
Comment (by robe):

 Mark,
 I fail to see why its non-deterministic. The plpgsql call will be doing
 exactly the same thing as our CREATE ... is doing now except possibly
 doing more inspection to see that we have remnants of other installs in
 there.  Like observer that the type that exists is incompatible with what
 we are loading etc.

 I'm more concerned that we are leaving things out in the
 postgis_upgrade.sql.  As I mentioned before we left out a cast in
 postgis_upgrade.sql that exists in the regular postgis.sql file.

 The way I see it. We have to double input stuff to generate postgis.sql
 and postgis_upgrade.sql which is more time consuming and prone to error.
 I'm not so much against having 2 files as I am about this problem.

 If we can put some flags in for postgis.sql.in.c so we can replace the
 create  etc. with a plpgsql function, I would be very happy.  Then we can
 have just one script to generate the postgis.sql and postgis_upgrade.sql
 file.  As it is I basically just use the postgis.sql and wipe out all the
 create stuff to guarantee I am getting everything.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/202#comment:20>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS