Re: PG 14 release notes, first draft

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PG 14 release notes, first draft
Date: 2021-05-10 14:00:05
Message-ID: 20210510140005.GB27406@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks for putting it together.

I think these two should be merged:
| Remove containment operators @ and ~ from contrib modules cube, hstore, intarray, and seg (Justin Pryzby)
| Remove deprecated containment operators for built-in geometry data types (Justin Pryzby)

| Improve autovacuum's analyze of partitioned tables (Yuzuko Hosoya)
| DETAILS?

Should say: Autovacuum now analyzes partitioned tables.

| The server variable check_client_connection_interval allows supporting operating systems, e.g., Linux, to automatically cancel queries by disconnected clients.
The GUC is actually called client_connection_check_interval - the commit
message used the wrong name.

| This is particularly helpful for reducing index bloat on tables that frequently update indexed columns.
Does it mean "..where indexed columns are frequently updated"?

| Allow multiple foreign table scans to be run in parallel (Robert Haas, Kyotaro Horiguchi, Thomas Munro, Etsuro Fujita)
I think it means multiple foreight table scan *nodes*

| If server variable compute_query_id is enabled, display the hash in pg_stat_activity, EXPLAIN VERBOSE, csvlog, and optionally in log_line_prefix (Julien Rouhaud)
I think needs details, like: "If disabled, then the hash might be computed by
an extension, instead".

Later, you say:
| Extension pg_stat_statements will need to enable hash computation via the compute_query_id server variable to function properly. pg_stat_statements can now use a custom hash computation method.
Maybe it should say "will need hash computation to be enabled".

| Allow more than the common name (CN) to be matched for client certificate authentication (Andrew Dunstan)
Your description makes it sound like arbitrary attributes can be compared. But
the option just allows comparing CN or DN.

| Allow file system sync at the start of crash recovery on Linux (Thomas Munro)
I think this should describe the existing, default behavior:
Allow syncfs method to sync data directory during recovery;
The default behavior is to open and fsync every data file, and the new setting
recovery_init_sync_method=syncfs instead syncs each filesystem in the data
directory.

| Add date_bin function (John Naylor)
This truncate timestamps on an arbitrary interval.
Like date_trunc() but also supports eg. '15 minutes', and also uses an arbitrary "origin".

| Support negative indexes in split_part() (Nikhil Benesch)
| Negative values count from the last field going forward.
should say "start from the last field and count backward" ?

| Add configure option --with-openssl to behave like --with-ssl={openssl} (Daniel Gustafsson, Michael Paquier)
| The option --with-openssl is kept for compatibility.
I think this is backwards. The new option is with-ssl=openssl, and (as you
said) with-openssl is kept.

Should these be in the "compatibility" section?

| Force custom server variable names to match the pattern used for unquoted SQL identifiers (Tom Lane)

| Change password_encryption's default to scram-sha-256 (Peter Eisentraut)

| Change checkpoint_completion_target default to 0.9 (Stephen Frost)

| Reduce the default value of vacuum_cost_page_miss (Peter Geoghegan)

Nitpicks to follow:

| Allow some GiST index to be built by presorting the data (Andrey Borodin)
indexes

| with --with-lz4 support to enable this feature
I would change to say "to support" rather than "support to enable"

| Speed truncation of small tables on large shared buffer servers (Kirk Jamison)
"on servers with large settings of shared_buffers"

| Allow windowing functions to perform incremental sorts (David Rowley)
Just "window" functions

| Improve pg_stat_activity reporting for walsenders processes (Tom Lane)
walsender

| Previously these functions could only be executed by super-users, and still defaults do that.
..which is still the default behavior.

| This allows multiple queries to be send and only wait for completion when a specific synchronization message is sent.
be sent

| Enhance libpq libpq's target_session_attrs parameter options (Haribabu Kommi, Greg Nancarrow, Vignesh C, Tom Lane)
remove first "libpq"

| With the removal of the ! operator in this release, factorial() is the only built-in way to computer a factorial.
compute

| For example, GROUP BY CUBE (a,b), CUBE (b,c) will generated duplicate grouping combinations without DISTINCT.

will generate

| Allow VACUUM VERBOSE to report page deletion counts for each scan of an index (Peter Geoghegan)

I think "Allow" is wrong - should just say that VACUUM VERBOSE reports..

|By default, only the root of partitioned tables are imported.
*is* imported

Can these be merged:
Allow logical replication to stream long transactions to standbys (Dilip Kumar, Tomas Vondra, Amit Kapila, Nikhil Sontakke)
Improve the logical replication API to allow streaming large in-progress transactions (Tomas Vondra, Dilip Kumar, Amit Kapila)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-05-10 14:09:40 Re: Inaccurate error message when set fdw batch_size to 0
Previous Message Antonin Houska 2021-05-10 13:56:56 Re: [PATCH] Full support for index LP_DEAD hint bits on standby