Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1kIEPC-0007X0-Tr
	for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Sep 2020 17:06:10 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1kIEPB-0006CM-Pi
	for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Sep 2020 17:06:09 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1kIEPB-0006CF-J4
	for pgsql-hackers@lists.postgresql.org; Tue, 15 Sep 2020 17:06:09 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1kIEP5-0003XB-Bn; Tue, 15 Sep 2020 17:06:08 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 08FH5xT21335041;
	Tue, 15 Sep 2020 13:05:59 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
cc: Masahiko Sawada <masahiko.sawada@2ndquadrant.com>,
        Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
        Bruce Momjian <bruce@momjian.us>,
        PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
In-reply-to: <6a0737be-53a2-2505-e46e-8c4b2929fa44@postgresql.org>
References: <20200505031600.GB21752@momjian.us>
 <448a382b-ae07-3126-5a08-aacda9aa28ea@postgresql.org>
 <f1c43223-3987-a23f-2063-18fd0aa4f0d4@2ndquadrant.com>
 <CA+fd4k606sc9y-hcmyqSRdEZMoa6uMAHSLFCdFa4bC_W4FkbwQ@mail.gmail.com>
 <63d3f3aa-e42d-dd3d-643c-2e91a13a0762@postgresql.org>
 <e0a4d177-d003-8ebb-5296-5a445472b66f@postgresql.org>
 <1305217.1600184757@sss.pgh.pa.us>
 <ad54fe2c-8692-d538-3406-b246343c2198@postgresql.org>
 <1306101.1600185943@sss.pgh.pa.us>
 <6a0737be-53a2-2505-e46e-8c4b2929fa44@postgresql.org>
Comments: In-reply-to "Jonathan S. Katz" <jkatz@postgresql.org>
	message dated "Tue, 15 Sep 2020 12:12:16 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1335039.1600189559.1@sss.pgh.pa.us>
Date: Tue, 15 Sep 2020 13:05:59 -0400
Message-ID: <1335040.1600189559@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

"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