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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: PostGIS Development Discussion <postgis-devel(at)lists(dot)osgeo(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [postgis-devel] About EXTENSION from UNPACKAGED on PostgreSQL 13
Date: 2020-02-26 15:37:41
Message-ID: 20200226153741.GE3195@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greetings,

* Sandro Santilli (strk(at)kbt(dot)io) wrote:
> On pgsql-hackers we only want to find a future-proof way to "package
> existing objects into an extension". If the syntax
> `CREATE EXTENSION <extname> FROM UNPACKAGED`
> has gone, would it be ok for just:
> `CREATE EXTENSION <extname>`
> to intercept unpackaged objects and package them ?

No. The reason it was removed is because it's not going to be safe to
do when we have trusted extensions. Perhaps it would be possible to
figure out a way to make it safe, but the reason FROM UNPACKAGED was
created and existed doesn't apply any more. That PostGIS has been using
it for something else entirely is unfortunate, but the way to address
what PostGIS needs is to talk about that, not talk about how this ugly
hack used to work and doesn't any more.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-02-26 15:45:16 Re: Commit fest manager for 2020-03
Previous Message Tom Lane 2020-02-26 15:36:07 Re: truncating timestamps on arbitrary intervals