| From: | Robert Treat <rob(at)xzilla(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | John Naylor <johncnaylorls(at)gmail(dot)com>, Richard Guo <guofenglinux(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: First draft of PG 19 release notes |
| Date: | 2026-05-12 02:34:47 |
| Message-ID: | CABV9wwNTftT4qiONveV1HVnbyAqM90NarfOGUZWbLhnggRkeug@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 11, 2026 at 5:42 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Mon, May 11, 2026 at 12:40:38PM +0700, John Naylor wrote:
> > On Wed, Apr 15, 2026 at 8:19 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > Hi Bruce, thanks for you work on this. Here are some comments:
> >
<snip>
> > > 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.
Robert Treat
https://xzilla.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-05-12 03:30:53 | Re: Fix unsafe PlannedStmt access in pg_stat_statements |
| Previous Message | Chao Li | 2026-05-12 02:31:05 | Re: Fix REPACK with WITHOUT OVERLAPS replica identity indexes |