Re: [postgis-devel] About EXTENSION from UNPACKAGED on PostgreSQL 13

Sandro Santilli <strk@kbt.io>

From: Sandro Santilli <strk@kbt.io>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Stephen Frost <sfrost@snowman.net>, PostGIS Development Discussion <postgis-devel@lists.osgeo.org>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2020-02-26T15:06:14Z
Lists: pgsql-hackers
On Wed, Feb 26, 2020 at 03:35:46PM +0100, Daniel Gustafsson wrote:
> > On 26 Feb 2020, at 15:13, Sandro Santilli <strk@kbt.io> wrote:
> 
> > On pgsql-hackers we only want to find a future-proof way to "package
> > existing objects into an extension".
> 
> What is the longterm goal of PostGIS, to use this as a stepping stone to reach
> a point where no unpackaged extensions exist; or find a way to continue with
> the current setup except with syntax that isn't going away?

No unpackaged extension seems like a good goal in the long term.

> Overloading the same syntax for creating packaged as well as unpackaged
> extensions sounds like the wrong path to go down.

So what other options would we have to let people upgrade a running
postgis or postgis_raster outside of the EXTENSION mechanism ?

--strk;