[postgis-users] Allowing use of PostGIS EXTENSION w/out raster - how to migrate to no-raster

[Sandro Santilli]

On Mon, Oct 09, 2017 at 04:26:36AM -0400, Regina Obe wrote:
> Sandro wrote:
> >
> >  1) Move raster to its own extension "postgis_raster"
> >     See https://trac.osgeo.org/postgis/ticket/3888
> >
> >  2) Provide two versions of extension "postgis"
> >     See https://trac.osgeo.org/postgis/ticket/3890
> >
> >  - How do users migrate to postgis that doesn't have raster ?
> >   proposal 1: DROP EXTENSION postgis_raster
> >   proposal 2: ALTER EXTENSION postgis UPDATE TO '<x>noraster'
> >
> > Given the above, user needs to know the value of <x> with proposal 2 while
> > it doesn't with proposal 1. Or did you mean upon upgrade ?
> 
> Proposal 2: If you are migrating to a version that wasn't even compiled with
> raster support and you came from one that did, all you have to do is
> 
> ALTER EXTENSION postgis UPDATE;   and your raster type and functions would
> be dropped because the postgis.control file would have default being
> "2.5.0noraster"

So you either specify what you want (including version) or the
behavior depend on how the system postgis was built.
Is that considered acceptable behavior for users ?
And it confirms users need to know more things (they need to know
how postgis was compiled on the system).

--strk; 

  ()   Free GIS & Flash consultant/developer
  /\   https://strk.kbt.io/services.html