[postgis-tickets] [PostGIS] #3338: postgis extension no-raster version

PostGIS trac at osgeo.org
Sat Oct 24 10:55:31 PDT 2015


#3338: postgis extension no-raster version
----------------------+---------------------------
  Reporter:  robe     |      Owner:  robe
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 2.3.0
 Component:  postgis  |    Version:  2.0.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 There wouldn't be much.  Because

 1) it would only apply for raster, since that is already part of postgis
 (sfcgal is already a separate extension and so is everything else), geos I
 propose we make sure whatever version has all the functions we need is the
 minimum (you guys always fight me on this point which is one of the reason
 I'm very against liblwgeom being split off, cause then the issue is even
 worse than GEOS) and I already do enough fighting every minor release for
 GEOS.

 2) There will only be one set of postgis version extensions based on what
 you compile

 e.g. you either get the postgis with raster or the version without raster

 and I propose we only allow one version upgrade/downgrade path

 so postgis with raster for version 2.3.0 will only have a postgis-2.3.0
 -no-raster--postgis-2.3.0.sql

 not all the others that applied



 I think this is fine because I think it's rare people switch from a no-
 raster to a raster and vice versa.

 The more common case would be folks who had to install the scripts without
 support of extensions and those people would then just have to do


 {{{
     -- upgrade the old way with scripts
     CREATE EXTENSION postgis FROM unpackaged VERSION "2.3.0-no-raster";
 }}}

 and then from then on its


 {{{
 ALTER EXTENSION postgis UPDATE;
 }}}


 like everyone else.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3338#comment:12>
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.


More information about the postgis-tickets mailing list