Re: PostgreSQL 17 Beta 1 release announcement draft - Mailing list pgsql-hackers

On 5/23/24 8:00 AM, Alvaro Herrera wrote:
> Looks good.  Some minor changes:

Thanks for this - right at the deadline! :D

>> ### Query and Operational Performance Improvements
>>
>> PostgreSQL 17 builds on recent releases and continues to improve performance across the entire system.
[Vacuum](https://www.postgresql.org/docs/17/routine-vacuuming.html),the PostgreSQL process responsible for reclaiming
storage,has a new internal data structure that has shown up to a 20x memory reduction for vacuum,
 
> 
> This reads funny:
> "Vacuum ... has shown a memory reduction for vacuum"
> Maybe just removing the "for vacuum" words at the end of the phrase is a
> sufficient fix.

Fixed.

>> PostgreSQL 17 can now use both planner statistics and the sort order of [common table
expressions](https://www.postgresql.org/docs/17/queries-with.html)(aka [`WITH`
queries](https://www.postgresql.org/docs/17/queries-with.html))to further
 
> 
> Is usage of "aka" typical?  I would have expected "a.k.a." but maybe I'm
> just outdated.

Removed, just b/c I can't quickly verify this.

>> Finally, PostgreSQL 17 adds more explicit SIMD instructions, including AVX-512 support for the
[`bit_count](https://www.postgresql.org/docs/17/functions-bitstring.html)function.
 
> 
> Note the lack of closing backtick in [`bit_count`].

Fixed.

>> ### Developer Experience
>>
>> PostgreSQL 17 continues to build on the SQL/JSON standard, adding support for the `JSON_TABLE` features that can
convertJSON to a standard PostgreSQL table, and SQL/JSON constructor (`JSON`, `JSON_SCALAR`, `JSON_SERIALIZE`) and
queryfunctions (`JSON_EXISTS`, `JSON_QUERY`, `JSON_VALUE`). Notably, these features were originally planned for the
PostgreSQL15 release but were reverted during the beta period due to design considerations, which is one reason we ask
foryou to help us test features during beta! Additionally, PostgreSQL 17 adds more functionality to its `jsonpath`
implementation,including the ability to convert JSON values to different data types.
 
> 
> I'm not sure it's accurate to say that converting JSON values to
> different datatypes is part of the jsonpath implementation; as I
> understand, jsonpath is the representation used to search for elements
> within JSON values.  If you replace "including" with "and", the result
> seems reasonable.

Fixed.

>> PostgreSQL 17 adds a new connection parameter, `sslnegotation`, which allows PostgreSQL to perform direct TLS
handshakeswhen using [ALPN](https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation), eliminating a
networkroundtrip. PostgreSQL is registered as `postgresql` in the ALPN directory.
 
> 
> Typo here "sslnegotation" missing an i, sslnegotiation.

Fixed.

>> PostgreSQL 17 normalizes the parameters for `CALL` in
[`pg_stat_statements`](https://www.postgresql.org/docs/17/pgstatstatements.html),reducing the number of entries for
frequentlycalled stored procedures. Additionally, [`VACUUM` progress
reporting](https://www.postgresql.org/docs/devel/progress-reporting.html#VACUUM-PROGRESS-REPORTING)now shows the
progressof vacuuming indexes. PostgreSQL 17 also introduces a new view,
[`pg_wait_events`](https://www.postgresql.org/docs/17/view-pg-wait-events.html),which provides descriptions about wait
eventsand can be combined with `pg_stat_activity` to give more insight into why an active session is waiting.
Additionally,some information in the
[`pg_stat_bgwriter`](https://www.postgresql.org/docs/17/monitoring-stats.html#MONITORING-PG-STAT-BGWRITER-VIEW)view is
nowsplit out into the new
[`pg_stat_checkpointer`](https://www.postgresql.org/docs/17/monitoring-stats.html#MONITORING-PG-STAT-CHECKPOINTER-VIEW)
view.
> 
> Note use of one link to "/devel/" here.

Fixed.

Thanks!

Jonathan