MIME-Version: 1.0
References: <6d008414-3da4-4049-a585-0aa20da1bbce@postgresql.org>
In-Reply-To: <6d008414-3da4-4049-a585-0aa20da1bbce@postgresql.org>
From: David Rowley <dgrowleyml@gmail.com>
Date: Thu, 16 May 2024 14:42:37 +1200
Message-ID: <CAApHDvoUNLM3mnNU9Jt3qLKH-HEwgvF0ost3D4_t0R7c-+ipKg@mail.gmail.com>
Subject: Re: PostgreSQL 17 Beta 1 release announcement draft
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CAApHDvoUNLM3mnNU9Jt3qLKH-HEwgvF0ost3D4_t0R7c-%2BipKg%40mail.gmail.com>
Precedence: bulk

Thanks for writing that up. It's always exciting to see this each year.

On Thu, 16 May 2024 at 13:45, Jonathan S. Katz <jkatz@postgresql.org> wrote:
> * Please indicate if you believe there's a notable omission, or if we
> should omit any of these callouts

I'd say the streaming read stuff added in b5a9b18cd and subsequent
commits like b7b0f3f27 and 041b96802 are worth a mention. I'd be happy
to see this over the IS NOT NULL qual stuff that I worked on in there
or even the AVX512 bit counting. Speeding up a backwater aggregate
function is nice, but IMO, not compatible with reducing the number
reads.

There's some benchmarking in a youtube video:
https://youtu.be/QAYzWAlxCYc?si=L0UT6Lrf067ZBv46&t=237

> * Please indicate if a description is confusing - I'm happy to rewrite
> to ensure it's clearer.
>
> Please provide feedback no later than Wed 2024-05-22 18:00 UTC.

The only other thing I saw from a quick read was a stray "the" in "the
copy proceed even if the there is an error inserting a row."

David