Re: PG 13 release notes, first draft - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG 13 release notes, first draft
Date
Msg-id 1335040.1600189559@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG 13 release notes, first draft  ("Jonathan S. Katz" <jkatz@postgresql.org>)
Responses Re: PG 13 release notes, first draft  ("Jonathan S. Katz" <jkatz@postgresql.org>)
List pgsql-hackers
"Jonathan S. Katz" <jkatz@postgresql.org> writes:
> On 9/15/20 12:05 PM, Tom Lane wrote:
>> Ah.  OK, we can certainly extend it to mention that.  How about
>> (not bothering with markup yet)
>> 
>>  Remove support for upgrading unpackaged (pre-9.1) extensions (Tom Lane)
>> +
>> +The FROM option of CREATE EXTENSION is no longer supported.

> +1.

> With that in place, I'm more ambivalent to whether or not it's mentioned
> in the incompatibilities section as well, though would lean towards
> having a mention of it there as it technically is one. But I don't feel
> too strongly about it.

After thinking a bit, I'm inclined to agree that we should move it
to "Incompatibilities".  It is a core server change (third-party
extensions don't have a choice to opt out, as per postgis' issue),
and even if it's trivial, we have some even-more-trivial issues
listed there, like command tag changes.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: "Unified logging system" breaks access to pg_dump debug outputs
Next
From: Heikki Linnakangas
Date:
Subject: Re: Yet another fast GiST build