[postgis-devel] [PostGIS] #242: Go back to having different scripts version from postgis lib version

PostGIS trac at osgeo.org
Fri Nov 6 20:45:32 PST 2009

#242: Go back to having different scripts version from postgis lib version
  Reporter:  robe     |       Owner:  pramsey      
      Type:  defect   |      Status:  closed       
  Priority:  medium   |   Milestone:  postgis 1.4.1
 Component:  postgis  |     Version:               
Resolution:  wontfix  |    Keywords:               
Comment (by robe):

 Yes that was why I thought we needed this change, because a large part of
 the utility of no-API changes is gone if you have to keep on running
 upgrade scripts after each install on each postgis enabled database you

 From a large databases farm perspective -- I envisioned the db admin would
 run the PostGIS upgrade and spot check the first one to verify upgrade
 scripts had not changed and then call it a day.  if problems should arise
 he/she could then revert back to the old so/dll

 But evidentally no one else cares about this but me so I concede defeat
 Pauls's note:
 This raises an issue of policy which our "API stable" promise makes
 perhaps worth articulating: functionality should be implemented
 primarily in the C library. Otherwise we're going to have this issue,
 of "bugs in the SQL" which cannot be solved by a library drop-in, and
 that require extra DBA attention.

 If the goal of "no SQL upgrades" is paramount, then moving more code
 into C makes sense.


Ticket URL: <http://trac.osgeo.org/postgis/ticket/242#comment:5>
PostGIS <http://trac.osgeo.org/postgis/>

More information about the postgis-devel mailing list