Re: [postgis-devel] About EXTENSION from UNPACKAGED on PostgreSQL 13 - Mailing list pgsql-hackers

From Sandro Santilli
Subject Re: [postgis-devel] About EXTENSION from UNPACKAGED on PostgreSQL 13
Date
Msg-id 20200226150614.GC27646@liz
Whole thread Raw
In response to Re: [postgis-devel] About EXTENSION from UNPACKAGED on PostgreSQL 13  (Daniel Gustafsson <daniel@yesql.se>)
List 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;



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Resolving the python 2 -> python 3 mess
Next
From: Alastair Turner
Date:
Subject: Re: Parallel copy