On 5/7/23 1:09 AM, Erik Rijkers wrote:
Op 5/7/23 om 05:37 schreef Jonathan S. Katz:Attached is a draft of the release announcement for the upcoming update release on May 11, 2023.Please provide any suggestions, corrections, or notable omissions no later than 2023-05-11 0:00 AoE.'leak in within a' should be 'leak within a'
Thanks for that catch! Revision attached. Jonathan
The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 15.3, 14.8, 13.11, 12.15, and 11.20. This release fixes over 80 bugs reported over the last several months. For the full list of changes, please review the [release notes](https://www.postgresql.org/docs/release/). PostgreSQL 11 EOL Notice ------------------------ PostgreSQL 11 will stop receiving fixes on November 9, 2023. If you are running PostgreSQL 11 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our [versioning policy](https://www.postgresql.org/support/versioning/) for more information. Bug Fixes and Improvements -------------------------- This update fixes over 80 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 15. Some of these issues may also affect other supported versions of PostgreSQL. Included in this release: * Several fixes for [`CREATE DATABASE`](https://www.postgresql.org/docs/current/sql-createdatabase.html) when using the `STRATEGY = WAL_LOG`, including a potential corruption that could lose modifications to a template/source database. * Fix crash with [`CREATE SCHEMA AUTHORIZATION`](https://www.postgresql.org/docs/current/sql-createschema.html). * Several fixes for [`MERGE`](https://www.postgresql.org/docs/current/sql-merge.html). * Several fixes for triggers in partitioned tables. * Disallow altering composite types that are stored in indexes. * Ensure that [`COPY TO`](https://www.postgresql.org/docs/current/sql-copy.html) from a parent table with [row-level security](https://www.postgresql.org/docs/current/ddl-rowsecurity.html) enabled does not copy any rows from child tables. * Adjust text-search-related character classification logic to correctly detect whether the prevailing locale is C when the default collation of a database uses the ICU provider. * Re-allow exponential notation in ISO-8601 interval fields. * Improve error reporting for various invalid JSON string literals. * Fix data corruption due to `vacuum_defer_cleanup_age` being larger than the current 64-bit xid. * Several fixes for the query parser and planner, including better detection of improperly-nested aggregates. * Fix partition pruning logic for partitioning on boolean columns when using a `IS NOT TRUE` condition. * Fix memory leak in [Memoize plan](https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-ENABLE-MEMOIZE) execution. * Fix buffer refcount leak on foreign tables using partitions when performing batched inserts. * Restore support for sub-millisecond `vacuum_cost_delay` settings. * Several fixes for [views and rules](https://www.postgresql.org/docs/current/rules-views.html). * Avoid unnecessary work while scanning a multi-column [BRIN index](https://www.postgresql.org/docs/current/brin.html) with multiple scan keys. * Ignore dropped columns and generated columns during logical replication of an `UPDATE` or `DELETE` action. * Several fixes for naming and availability of wait events. * Support RSA-PSS certificates with [SCRAM-SHA-256](https://www.postgresql.org/docs/current/sasl-authentication.html#SASL-SCRAM-SHA-256) channel binding. This feature requires building with OpenSSL 1.1.1 or newer. * Avoid race condition with process ID tracking on Windows. * Fix memory leak within a session for [PL/pgSQL](https://www.postgresql.org/docs/current/plpgsql.html) [`DO`](https://www.postgresql.org/docs/current/sql-do.html) blocks that use cast expressions. * Tighten array dimensionality checks from [PL/Perl](https://www.postgresql.org/docs/current/plperl.html) and [PL/Python](https://www.postgresql.org/docs/current/plpython.html) when converting list structures to multi-dimensional SQL arrays. * Fix [`pg_dump`](https://www.postgresql.org/docs/current/app-pgdump.html) so that partitioned tables that are hash-partitioned on an [enumerated type](https://www.postgresql.org/docs/current/datatype-enum.html) column can be restored successfully. * Fix for [`pg_trgm`](https://www.postgresql.org/docs/current/pgtrgm.html) where an unsatisfiable regular expression could lead to a crash when using a GiST or GIN index. * Limit memory usage of `pg_get_wal_records_info()` in [`pg_walinspect`](https://www.postgresql.org/docs/current/pgwalinspect.html). This release also updates time zone data files to tzdata release 2023c for DST law changes in Egypt, Greenland, Morocco, and Palestine. When observing Moscow time, Europe/Kirov and Europe/Volgograd now use the abbreviations MSK/MSD instead of numeric abbreviations, for consistency with other timezones observing Moscow time. Also, America/Yellowknife is no longer distinct from America/Edmonton; this affects some pre-1948 timestamps in that area. For the full list of changes available, please review the [release notes](https://www.postgresql.org/docs/release/). Updating -------- All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use `pg_upgrade` in order to apply this update release; you may simply shutdown PostgreSQL and update its binaries. Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details. For more details, please see the [release notes](https://www.postgresql.org/docs/release/). Links ----- * [Download](https://www.postgresql.org/download/) * [Release Notes](https://www.postgresql.org/docs/release/) * [Security](https://www.postgresql.org/support/security/) * [Versioning Policy](https://www.postgresql.org/support/versioning/) * [PostgreSQL 15 Release Announcement](https://www.postgresql.org/about/press/) * [Follow @postgresql on Twitter](https://twitter.com/postgresql) If you have corrections or suggestions for this release announcement, please send them to the _pgsql-www@lists.postgresql.org_ public [mailing list](https://www.postgresql.org/list/).
OpenPGP_signature
Description: OpenPGP digital signature
