Re: PG 16 draft release notes ready

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
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-05-25 01:31:29
Message-ID: CAFBsxsEMoNdg6CCMuQ-6YJ8G=AgGNMVuiTb5Di5bsoPfBb=9CA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 24, 2023 at 8:58 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> 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.

It looks like it got moved to Functions actually?

> > 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.

Looks good to me, although...

> Allow xid/subxid searches and ASCII string detection to use vector
operations (Nathan Bossart)

Nathan wrote the former, I did the latter.

Thanks for working on this!

--
John Naylor
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2023-05-25 02:02:49 Re: PG 16 draft release notes ready
Previous Message Andres Freund 2023-05-25 01:28:40 Re: Proposal: Removing 32 bit support starting from PG17++