PostgreSQL 17.10

What's new in this version:

Fixes and Improvements:
- This update fixes over 60 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 18. Some of these issues may also affect other supported versions of PostgreSQL.
- Fix queries that could return incorrect results when using a nondeterministic collation over a unique index.
- Fix loss of deferrability of foreign-key triggers. Previously, a foreign key defined as DEFERRABLE INITIALLY DEFERRED would behave as NOT DEFERRABLE after being set to NOT ENFORCED status and then back to ENFORCED. If you have a foreign key with this problem, after installing this update you can fix it by setting it to NOT ENFORCED and then back to ENFORCED.
- Improve the planner's ability to apply partition pruning to more cases.
- Fix self-join removal to handle join clauses that are only boolean columns, for example, ON t1.boolcol.
- Several fixes around virtual generated columns, including ensuring INSERT ... ON CONFLICT works when EXCLUDED references a virtual generated column.
- Report a serialization failure when MERGE encounters a concurrently-updated tuple in "repeatable read" or "serializable" isolation modes.
- Fix CREATE TABLE ... LIKE ... INCLUDING STATISTICS for cases where the source table had one or more dropped columns
- Fix WITHOUT OVERLAPS to allow domains
- Disallow making a composite type be a member of itself via a multirange
- Fix sometimes-incorrect results when array_agg(anyarray) executes in parallel
- Prevent bloating during restore of an incremental backup
- Prevent stuck logical replication slot synchronization worker processes from blocking promotion of a standby server
- Make the pg_aios system view pid column show NULL instead of 0 when an entry has no owning process
- Fix cases where pg_stat_replication shows NULL lag even while replication is active
- Correctly display JOIN alias variables that are used in GROUP BY
- If the startup process fails, properly shut down other child processes before exiting the postmaster
- Fix race condition that could cause a standby server following WAL from a primary of an older minor version to get into a crash-and-restart loop.
- Prevent indefinite wait in shutdown of a walsender process when logical replication is actively publishing data
- Ensure that free space map changes are persisted during recovery. This could have performance ramifications on a standby server after promotion.
- Fix assorted bugs in backup decompression and tar-parsing code used in pg_basebackup and pg_verifybackup
- Ensure pg_dumpall doesn't skip role grants with dangling grantor OIDs, restoring the behavior before PostgreSQL 16. Emits a warning about missing grantor if the source server is PostgreSQL 16 or later.
- Fix pg_upgrade to use the correct protocol version when connecting to older source servers
- Fix output in pg_overexplain when using the RANGE_TABLE option
- Fix postgres_fdw crash due to premature cleanup of a failed connection