[postgis-tickets] [PostGIS] #3338: postgis extension that returns not supported for all Raster functions if raster not available

[PostGIS]

#3338: postgis extension that returns not supported for all Raster functions if
raster not available
----------------------+---------------------------
  Reporter:  robe     |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 2.3.0
 Component:  postgis  |    Version:  2.0.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by robe):

 ALTER EXTENSION UPDATE TO VERION "2.3.0next" would convert a non-raster
 postgis to a postgis one if the new one was compiled with raster.  In fact
 it would be even easier if they started with no raster in version 2.3.0
 and put raster in 2.3.1.

 The issue I have with postgis_core/postgis_raster is

 1) two steps for everybody (I know a lot of people don't want raster so
 not a big deal)
 2) to do create extension postgis (until 9.6 comes along) would be  3 step
 process (yah I know for legacy)
 3) We'd have to tell folks like pgrouting to change their required to
 postgis_core (and that isn't backward compatible for them) so that sucks.
 4) Everyone is used to doing CREATE EXTENSION postgis; to get everything

 So the only other least painful alternative would
 to have our postgis upgrade script drop raster functions from the
 extension.

 Then they do


 {{{
 CREATE EXTENSION postgis_raster from unpackaged;
 }}}

 and we continue life from there telling people they need to install
 postgis_raster in future.

 That does have the benefit that if a package DOES depend on
 postgis_raster, then they can state that and wouldn't be screwed by a
 postgis extension SANS raster.

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