From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 16 draft release notes ready |
Date: | 2023-05-24 13:58:00 |
Message-ID: | ZG4X6EUdoTitXSP1@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 24, 2023 at 12:23:02PM +0700, John Naylor wrote:
>
> On Wed, May 24, 2023 at 11:19 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > Second, you might be correct that the section is wrong. I thought of
> > CPU instructions as something tied to the compiler, so part of the build
> > process or source code, but the point we should be make is that we have
> > these acceleration, not how it is implemented. We can move the entire
> > group to the "General Performance" section, or we can split it out:
>
> Splitting out like that seems like a good idea to me.
Okay, items split into sections and several merged. I left the
CPU-specific parts in Source Code, and moved the rest into a merged item
in General Performance, but moved the JSON item to Data Types.
Patch attached, and you can see the results at:
https://momjian.us/pgsql_docs/release-16.html
> The last one refers to new internal functions, so it could stay in source code.
> (Either way, we don't want to imply that arrays of SQL types are accelerated
> this way, it's so far only for internal arrays.)
Good point. I called them "C arrays" but it it into the General
Performance item.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
Attachment | Content-Type | Size |
---|---|---|
vector.diff | text/x-diff | 3.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tristan Partin | 2023-05-24 13:58:46 | Re: Make pgbench exit on SIGINT more reliably |
Previous Message | Tomas Vondra | 2023-05-24 13:38:41 | Re: memory leak in trigger handling (since PG12) |