Re: First draft of PG 19 release notes

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: John Naylor <johncnaylorls@gmail.com>
Cc: Robert Treat <rob@xzilla.net>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2026-05-12T19:11:16Z
Lists: pgsql-hackers

Attachments

On Tue, May 12, 2026 at 10:38:40AM +0700, John Naylor wrote:
> On Tue, May 12, 2026 at 9:35 AM Robert Treat <rob@xzilla.net> wrote:
> >
> > On Mon, May 11, 2026 at 5:42 PM Bruce Momjian <bruce@momjian.us> wrote:
> > > On Mon, May 11, 2026 at 12:40:38PM +0700, John Naylor wrote:
> > > > > Optionally use AVX2 CPU instructions for calculating page checksums (Matthew Sterrett, Andrew Kim) §
> > > >
> > > > > Optionally use ARM Crypto Extension to Compute CRC32C (John Naylor) §
> > > >
> > > > There's no option for these, the extensions are used where available.
> > >
> > > So, the "Optionally" indicates we use these instructions if the CPU
> > > supports them.  I assume we don't use them on all CPUs.  Can you
> > > suggest better wording?
> > >
> >
> > I think the simplest change would be to replace "optionally" with
> > "when available", although ISTR we use wording along the lines of "Add
> > support for" or "is now supported" when runtime/compiler checks are
> > involved.
> 
> That would be fine. The v17 and v18 release notes didn't have such
> qualifying language, for things that are less common than the above
> (SVE, AVX-512), but whatever.

Okay, I will just remove the "Optionally" and see if anyone complains.
Patch attached and applied.

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

  Do not let urgent matters crowd out time for investment in the future.