From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL 17 Beta 1 release announcement draft |
Date: | 2024-05-16 10:41:50 |
Message-ID: | CAGECzQR+MUTGYXfWojVQXfd1x-wzJUCDaLTppDs8_7X57ucUhQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 16 May 2024 at 03:45, Jonathan S. Katz <jkatz(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robins Tharakan | 2024-05-16 10:48:43 | Re: Why is parula failing? |
Previous Message | Peter Eisentraut | 2024-05-16 10:29:08 | Re: [PATCH] Add --syntax to postgres for SQL syntax checking |