Re: PG 16 draft release notes ready

From: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 16 draft release notes ready
Date: 2023-06-05 08:33:51
Message-ID: 20230605173351.fb4effbb5bc8ed12871de65f@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

On Thu, 18 May 2023 16:49:47 -0400
Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> I have completed the first draft of the PG 16 release notes. You can
> see the output here:

Thanks for the release notes.

>
> https://momjian.us/pgsql_docs/release-16.html
>
> I will adjust it to the feedback I receive; that URL will quickly show
> all updates.

I didn't find the following in the release note. This might be
considered as a bug fix, but the change in this commit can potentially
impact applications. Is it worth including it in the release note?

commit 43351557d0d2b9c5e20298b5fee2849abef86aff
Make materialized views participate in predicate locking

Regards,
Yugo Nagata

> I learned a few things creating it this time:
>
> * I can get confused over C function names and SQL function names in
> commit messages.
>
> * The sections and ordering of the entries can greatly clarify the
> items.
>
> * The feature count is slightly higher than recent releases:
>
> release-10: 189
> release-11: 170
> release-12: 180
> release-13: 178
> release-14: 220
> release-15: 184
> --> release-16: 200
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
> EDB https://enterprisedb.com
>
> Only you can decide what is important to you.
>
>

--
Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Pyhalov 2023-06-05 09:00:27 Re: Partial aggregates pushdown
Previous Message torikoshia 2023-06-05 08:30:18 Re: RFC: Logging plan of the running query