From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: 2022-08-11 release announcement draft |
Date: | 2022-08-08 18:35:25 |
Message-ID: | 63399018-6cf0-10c3-b760-eb69b643be27@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/8/22 12:44 PM, Justin Pryzby wrote:
> On Mon, Aug 08, 2022 at 11:50:16AM -0400, Jonathan S. Katz wrote:
>> * Fix [`pg_upgrade`](https://www.postgresql.org/docs/current/pgupgrade.html) to
>> detect non-upgradable usages of functions accepting `anyarray` parameters.
>
> use or usage
This line comes directly from the release notes and appears to be
correct as is.
>> and regressions before the general availability of PostgreSQL 15. As
>> this is a beta release , changes to database behaviors, feature details,
>
> Extraneous space before comma
Fixed.
>> APIs are still possible. Your feedback and testing will help determine the final
>
> and APIs
Fixed.
>> tweaks on the new features, so please test in the near future. The quality of
>
> remove "new" before features ?
I believe this is personal preference. I would like to leave in "new" as
we are releasing new features in PostgreSQL 15.
Thanks,
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Cleveland | 2022-08-08 18:40:00 | Managing my own index partitions |
Previous Message | Marcos Pegoraro | 2022-08-08 18:34:27 | Re: bug on log generation ? |