| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 13 release notes, first draft |
| Date: | 2020-09-15 18:05:24 |
| Message-ID: | 10ed2406-11f9-8297-6e4e-2849a8fa6ed4@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/15/20 1:05 PM, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)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 | Content-Type | Size |
|---|---|---|
| create-extension-from-v2.patch | text/plain | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-09-15 18:11:01 | Re: PG 13 release notes, first draft |
| Previous Message | Andres Freund | 2020-09-15 18:04:13 | Re: Allow ERROR from heap_prepare_freeze_tuple to be downgraded to WARNING |