| 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:25:27 |
| Message-ID: | 4d057fbb-1531-7273-92dd-f06c44b76304@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/15/20 2:11 PM, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
>> On 9/15/20 1:05 PM, Tom Lane wrote:
>>> 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?
>
> The other incompatibilities are only listed once, if they're minor.
> I was just about to commit the attached.
Even better. +1
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-09-15 18:30:29 | Re: PG 13 release notes, first draft |
| Previous Message | Tom Lane | 2020-09-15 18:11:01 | Re: PG 13 release notes, first draft |