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

From Jonathan S. Katz
Subject Re: PG 13 release notes, first draft
Date
Msg-id 10ed2406-11f9-8297-6e4e-2849a8fa6ed4@postgresql.org
Whole thread Raw
In response to Re: PG 13 release notes, first draft  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PG 13 release notes, first draft  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 9/15/20 1:05 PM, Tom Lane wrote:
> "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.

How about this?

Jonathan

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Allow ERROR from heap_prepare_freeze_tuple to be downgraded to WARNING
Next
From: Tom Lane
Date:
Subject: Re: PG 13 release notes, first draft