Date: Thu, 18 May 2023 21:45:33 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 16 draft release notes ready
Message-ID: <ZGbUvU2SdEViXrrM@momjian.us>
References: <ZGaPa7M3gc2THeDJ@momjian.us>
 <CAEze2Witdt9YHZ=E3ouHFrpfGmRiub=HWsmy9x=VStrDHx0wFg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAEze2Witdt9YHZ=E3ouHFrpfGmRiub=HWsmy9x=VStrDHx0wFg@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/ZGbUvU2SdEViXrrM%40momjian.us>
Precedence: bulk

On Fri, May 19, 2023 at 01:33:17AM +0200, Matthias van de Meent wrote:
> On Thu, 18 May 2023 at 22:49, Bruce Momjian <bruce@momjian.us> wrote:
> >
> > I have completed the first draft of the PG 16 release notes.  You can
> > see the output here:
> >
> >         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'm not sure if bugfixes like these are considered for release notes,
> but I'm putting it up here just in case:
> 
> As of 8fcb32db (new, only in PG16) we now enforce limits on the size
> of WAL records during construction, where previously we hoped that the
> WAL records didn't exceed those limits.
> This change is immediately user-visible through a change in behaviour
> of `pg_logical_emit_message(true, repeat('_', 2^30 - 10), repeat('_',
> 2^30 - 10))`, and extensions that implement their own rmgrs could also
> see a change in behavior from this change.

I saw that commit but I considered it sufficiently rare and sufficiently
internal that I did not include it.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.