From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Darafei "Komяpa" Praliaskouski <me(at)komzpa(dot)net> |
Cc: | 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 21:00:47 |
Message-ID: | 19541.1582664447@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
=?UTF-8?Q?Darafei_=22Kom=D1=8Fpa=22_Praliaskouski?= <me(at)komzpa(dot)net> writes:
> 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.
I'd agree with Stephen's comment:
> On Tue, Feb 25, 2020 at 11:37 PM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>> Why is it impacting the PostGIS upgrade path? The FROM UNPACKAGED was
>> never intended to be used as an upgrade path..
This seems like a serious abuse of the FROM option, not to mention being
fundamentally unsafe --- the whole problem with FROM is that you can't
be entirely sure what the starting state is. So unless you can make a
pretty strong case as to why you need to do it like that, and that there's
no other way to handle it in the many months before v13 ships, I'm not
going to have a lot of sympathy.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rémi Lapeyre | 2020-02-25 21:38:32 | [PATCH v1] Allow COPY "test" to output a header and add header matching mode to COPY FROM |
Previous Message | Darafei Komяpa Praliaskouski | 2020-02-25 20:52:47 | Re: [postgis-devel] About EXTENSION from UNPACKAGED on PostgreSQL 13 |