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

From: Darafei "Komяpa" Praliaskouski <me(at)komzpa(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-25 20:52:47
Message-ID: CAC8Q8tKX5AO9f+sfxWNLHw=he4GN7bif07o2__tERQXexRd4Tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

PostGIS 2.5 had raster and vector blended together in single extension.
In PostGIS 3, they were split out into postgis and postgis_raster extensions.
To upgrade, there is now postgis_extensions_upgrade() function, that
unpackages the raster part out of postgis extensions, upgrades it, and
packages raster functions back into postgis_raster by utilizing FROM
UNPACKAGED.
Removal of FROM UNPACKAGED breaks PostGIS 2.5 -> 3.0 upgrade path, and
we haven't yet found a proper replacement since such removal wasn't
something we were expecting.

On Tue, Feb 25, 2020 at 11:37 PM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
> Greetings,
>
> * Darafei "Komяpa" Praliaskouski (me(at)komzpa(dot)net) wrote:
> > can it be raised on pgsql-hackers as a thing impacting PostGIS upgrade path?
>
> Why is it impacting the PostGIS upgrade path? The FROM UNPACKAGED was
> never intended to be used as an upgrade path..
>
> Thanks,
>
> Stephen
> _______________________________________________
> postgis-devel mailing list
> postgis-devel(at)lists(dot)osgeo(dot)org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel

--
Darafei Praliaskouski
Support me: http://patreon.com/komzpa

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-02-25 21:00:47 Re: [postgis-devel] About EXTENSION from UNPACKAGED on PostgreSQL 13
Previous Message Cary Huang 2020-02-25 20:50:18 Re: Internal key management system