[postgis-devel] Pg13 upgrade issues?

[Paul Ramsey]

> On Sep 15, 2020, at 9:53 AM, Sandro Santilli <strk at kbt.io> wrote:
> 
> On Tue, Sep 15, 2020 at 06:39:24PM +0200, rmrodriguez at carto.com wrote:
>> I've been wondering about this and thought about another solution that I
>> think is simpler: We could have postgis (core) drop any types and functions
>> owned by it that now belong to postgis_raster.
>> 
>> The main benefit would be that it will work no matter the PG release or the
>> source Postgis release. The drawbacks: any dependency on raster (views and
>> so on) will need to be dropped in this process (only once) and that you
>> need to install postgis_raster if you use raster (beforehand the functions
>> were already there).
> 
> And actual data ! Sounds very drastic, why would this be simpler than
> packaging on 'CREATE EXTENSION' ?

Are you proposing direct editing the pg_extension and pg_depend tables to package the existing functions?
We still have the limitation that we cannot create an extension within another create extension, if I'm not mistaken?
I tried your PR, and the core idea of a fake 'unpackaged' target seems miraculously to work, so there's just some polish to be added to the PR as far as I can tell. What do you feel are the drawbacks of it? The further we get away from 2.X, the less the "hackiness" of the solution matters in practical terms.

P