MIME-Version: 1.0
References: <6d008414-3da4-4049-a585-0aa20da1bbce@postgresql.org>
In-Reply-To: <6d008414-3da4-4049-a585-0aa20da1bbce@postgresql.org>
From: Jelte Fennema-Nio <postgres@jeltef.nl>
Date: Thu, 16 May 2024 12:41:50 +0200
Message-ID: <CAGECzQR+MUTGYXfWojVQXfd1x-wzJUCDaLTppDs8_7X57ucUhQ@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/CAGECzQR%2BMUTGYXfWojVQXfd1x-wzJUCDaLTppDs8_7X57ucUhQ%40mail.gmail.com>
Precedence: bulk

On Thu, 16 May 2024 at 03:45, Jonathan S. Katz <jkatz@postgresql.org> wrote:
> Attached is a copy of the PostgreSQL 17 Beta 1 release announcement
> draft.

I think we can quickly mention c4ab7da6061 in the COPY paragraph, in
some benchmarks it improved perf by close to 2x. Something like this:
"has improved performance in PostgreSQL 17 when the source encoding
matches the destination encoding *and when sending large rows from
server to client*"

Also, I think it's a bit weird to put the current COPY paragraph under
Developer Experience. I think if you want to keep it there instead of
move it to the per section, we should put the line about IGNORE_ERROR
first instead of the perf improvements. Now the IGNORE_ERROR addition
seems more of an afterthought.

s/IGNORE_ERROR/ON_ERROR

I think it would be good to clarify if the following applies when
upgrading from or to PostgreSQL 17:
"Starting with PostgreSQL 17, you no longer need to drop logical
replication slots when using pg_upgrade"

Finally, I personally would have included a lot more links for the new
items in this document. Some that would benefit from being a link
imho:
- pg_createsubscriber
- JSON_TABLE
- SQL/JSON constructor
- SQL/JSON query functions
- ON_ERROR
- sslnegotiation
- PQchangePassword
- pg_maintain