Re: 2023-11-09 release announcement draft
On Tue, Nov 07, 2023 at 09:02:03AM -0500, Jonathan S. Katz wrote: > On 11/6/23 9:52 PM, Noah Misch wrote: > > On Mon, Nov 06, 2023 at 05:04:25PM -0500, Jonathan S. Katz wrote: > > Delete lines starting here ... > > > > > This is the **final release of PostgreSQL 11**. PostgreSQL 10 will no > > > longer > > > receive > > > [security and bug fixes](https://www.postgresql.org/support/versioning/). > > > If you are running PostgreSQL 10 in a production environment, we suggest > > > that > > > you make plans to upgrade. > > > > ... to here. They're redundant with "PostgreSQL 11 EOL Notice" below: > > Initially, I strongly disagreed with this recommendation, as I've seen > enough people say that they were unaware that a community version is EOL. We > can't say this enough. > > However, I did decide to clip it out because the notice is just below. I just figured it was a copy-paste error, given the similarity of nearby sentences. I have no concern with a general goal of saying more about the end of v11.
Re: 2023-11-09 release announcement draft
On 11/6/23 9:52 PM, Noah Misch wrote: On Mon, Nov 06, 2023 at 05:04:25PM -0500, Jonathan S. Katz wrote: The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 16.1, 15.5, 14.10, 13.13, 12.17, and 11.22 This release fixes over 55 bugs reported over the last several months. This release includes fixes for indexes where in certain cases, we advise reindexing. Please see the "Update" section for more details. s/"Update" section/"Updating" section/ or change section title below. Fixed. Delete lines starting here ... This is the **final release of PostgreSQL 11**. PostgreSQL 10 will no longer receive [security and bug fixes](https://www.postgresql.org/support/versioning/). If you are running PostgreSQL 10 in a production environment, we suggest that you make plans to upgrade. ... to here. They're redundant with "PostgreSQL 11 EOL Notice" below: Initially, I strongly disagreed with this recommendation, as I've seen enough people say that they were unaware that a community version is EOL. We can't say this enough. However, I did decide to clip it out because the notice is just below. That said, perhaps we should put out a separate announcement that states PostgreSQL 11 is EOL. We may want to consider doing standalone EOL announcement -- perhaps 6 months out, and then day of, to make it abundantly clear that a version is deprecating. Finally, I included Matthias' downthread recommendation in this version. Thanks, Jonathan The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 16.1, 15.5, 14.10, 13.13, 12.17, and 11.22 This release fixes over 55 bugs reported over the last several months. This release includes fixes for indexes where in certain cases, we advise reindexing. Please see the "Updating" section for more details. For the full list of changes, please review the [release notes](https://www.postgresql.org/docs/release/). PostgreSQL 11 EOL Notice **This is the final release of PostgreSQL 11**. PostgreSQL 11 is now end-of-life and will no longer receive security and bug fixes. 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 55 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 16. Some of these issues may also affect other supported versions of PostgreSQL. * Fix issue where GiST indexes had an incorrect behavior during a "page split" operation that could lead to incorrect results in subsequent index searches. Please [reindex](https://www.postgresql.org/docs/current/sql-reindex.html) GiST indexes after installing this update. * Fix issue where B-tree indexes would incorrectly de-duplicate `interval` columns. Please [reindex](https://www.postgresql.org/docs/current/sql-reindex.html) any B-tree index that includes an `interval` column after installing this update. * Provide more efficient indexing of `date`, `timestamptz`, and `timestamp` values in BRIN indexes when using a [`minmax_multi` opsclass](https://www.postgresql.org/docs/current/brin-builtin-opclasses.html). While not required, we recommend [reindexing](https://www.postgresql.org/docs/current/sql-reindex.html) BRIN indexes that include these data types after installing this update. * Fix for bulk table insertion into partitioned tables. * Fix for hash-partitioned tables with multiple partition keys during step generation and runtime pruning that could lead to crashes in some cases. * Throw the correct error if [`pgrowlocks()`](https://www.postgresql.org/docs/current/pgrowlocks.html) is applied to a partitioned table * Fix inconsistent rechecking of concurrently-updated rows during [`MERGE`](https://www.postgresql.org/docs/current/sql-merge.html) when using [`READ COMMITTED`](https://www.postgresql.org/docs/current/transaction-iso.html#XACT-READ-COMMITTED) mode. * Correctly identify the target table in an inherited `UPDATE`/`DELETE`/`MERGE` even when the parent table is excluded by constraints. * Fix over-allocation of a constructed [`tsvector`](https://www.postgresql.org/docs/current/datatype-textsearch.html#DATATYPE-TSVECTOR). * Fix [`ALTER SUBSCRIPTION`](https://www.postgresql.org/docs/current/sql-altersubscription.html) to apply changes in the `run_as_owner` option. * Several fixes for [`COPY FROM`](https://www.postgresql.org/docs/current/sql-copy.html), * Several fixes for handling torn reads with [`pg_control`](https://www.postgresql.org/docs/current/wal-internals.html). * Fix "could not find pathkey item to sort" errors occurring while planning aggregate functions with `ORDER BY` or `DISTINCT` options. * When
Re: 2023-11-09 release announcement draft
On Mon, 6 Nov 2023 at 23:04, Jonathan S. Katz wrote: > > Hi, > > Attached is the release announcement draft for the 2023-11-09 release > (16.1 et al.). > > Please review for accuracy and notable omissions. Please have all > feedback in by 2023-11-09 08:00 UTC at the latest (albeit the sooner the > better). > 20231109updaterelease.md > [...] > * Provide more efficient indexing of `date`, `timestamptz`, and `timestamp` > values in BRIN indexes. While not required, we recommend > [reindexing](https://www.postgresql.org/docs/current/sql-reindex.html) BRIN > indexes that include these data types after installing this update. As the type's minmax_multi opclasses are marked as default, I believe it makes sense to explicitly mention that only indexes that use the type's minmax_multi opclasses would need to be reindexed for them to see improved performance. The types' *_bloom and *_minmax opclasses were not affected and therefore do not need to be reindexed. Kind regards, Matthias van de meent.
Re: 2023-11-09 release announcement draft
On Mon, Nov 06, 2023 at 05:04:25PM -0500, Jonathan S. Katz wrote: > The PostgreSQL Global Development Group has released an update to all > supported > versions of PostgreSQL, including 16.1, 15.5, 14.10, 13.13, 12.17, and 11.22 > This release fixes over 55 bugs reported over the last several months. > > This release includes fixes for indexes where in certain cases, we advise > reindexing. Please see the "Update" section for more details. s/"Update" section/"Updating" section/ or change section title below. Delete lines starting here ... > This is the **final release of PostgreSQL 11**. PostgreSQL 10 will no longer > receive > [security and bug fixes](https://www.postgresql.org/support/versioning/). > If you are running PostgreSQL 10 in a production environment, we suggest that > you make plans to upgrade. ... to here. They're redundant with "PostgreSQL 11 EOL Notice" below: > For the full list of changes, please review the > [release notes](https://www.postgresql.org/docs/release/). > > PostgreSQL 11 EOL Notice > > > **This is the final release of PostgreSQL 11**. PostgreSQL 11 is now > end-of-life > and will no longer receive security and bug fixes. 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.
Re: 2023-11-09 release announcement draft
Hi, On 11/6/23 17:04, Jonathan S. Katz wrote: Attached is the release announcement draft for the 2023-11-09 release (16.1 et al.). Please review for accuracy and notable omissions. Please have all feedback in by 2023-11-09 08:00 UTC at the latest (albeit the sooner the better). s/PostgreSQL 10/PostgreSQL 11/g Best regards, Jesper
2023-11-09 release announcement draft
Hi, Attached is the release announcement draft for the 2023-11-09 release (16.1 et al.). Please review for accuracy and notable omissions. Please have all feedback in by 2023-11-09 08:00 UTC at the latest (albeit the sooner the better). Thanks, Jonathan The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 16.1, 15.5, 14.10, 13.13, 12.17, and 11.22 This release fixes over 55 bugs reported over the last several months. This release includes fixes for indexes where in certain cases, we advise reindexing. Please see the "Update" section for more details. This is the **final release of PostgreSQL 11**. PostgreSQL 10 will no longer receive [security and bug fixes](https://www.postgresql.org/support/versioning/). If you are running PostgreSQL 10 in a production environment, we suggest that you make plans to upgrade. For the full list of changes, please review the [release notes](https://www.postgresql.org/docs/release/). PostgreSQL 11 EOL Notice **This is the final release of PostgreSQL 11**. PostgreSQL 11 is now end-of-life and will no longer receive security and bug fixes. 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 55 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 16. Some of these issues may also affect other supported versions of PostgreSQL. * Fix issue where GiST indexes had an incorrect behavior during a "page split" operation that could lead to incorrect results in subsequent index searches. Please [reindex](https://www.postgresql.org/docs/current/sql-reindex.html) GiST indexes after installing this update. * Fix issue where B-tree indexes would incorrectly de-duplicate `interval` columns. Please [reindex](https://www.postgresql.org/docs/current/sql-reindex.html) any B-tree index that includes an `interval` column after installing this update. * Provide more efficient indexing of `date`, `timestamptz`, and `timestamp` values in BRIN indexes. While not required, we recommend [reindexing](https://www.postgresql.org/docs/current/sql-reindex.html) BRIN indexes that include these data types after installing this update. * Fix for bulk table insertion into partitioned tables. * Fix for hash-partitioned tables with multiple partition keys during step generation and runtime pruning that could lead to crashes in some cases. * Throw the correct error if [`pgrowlocks()`](https://www.postgresql.org/docs/current/pgrowlocks.html) is applied to a partitioned table * Fix inconsistent rechecking of concurrently-updated rows during [`MERGE`](https://www.postgresql.org/docs/current/sql-merge.html) when using [`READ COMMITTED`](https://www.postgresql.org/docs/current/transaction-iso.html#XACT-READ-COMMITTED) mode. * Correctly identify the target table in an inherited `UPDATE`/`DELETE`/`MERGE` even when the parent table is excluded by constraints. * Fix over-allocation of a constructed [`tsvector`](https://www.postgresql.org/docs/current/datatype-textsearch.html#DATATYPE-TSVECTOR). * Fix [`ALTER SUBSCRIPTION`](https://www.postgresql.org/docs/current/sql-altersubscription.html) to apply changes in the `run_as_owner` option. * Several fixes for [`COPY FROM`](https://www.postgresql.org/docs/current/sql-copy.html), * Several fixes for handling torn reads with [`pg_control`](https://www.postgresql.org/docs/current/wal-internals.html). * Fix "could not find pathkey item to sort" errors occurring while planning aggregate functions with `ORDER BY` or `DISTINCT` options. * When [`track_io_timing`](https://www.postgresql.org/docs/current/runtime-config-statistics.html#GUC-TRACK-IO-TIMING) is enabled, include the time taken by relation extension operations as write time. * Track the dependencies of cached [`CALL`](https://www.postgresql.org/docs/current/sql-call.html) statements, and re-plan them when needed. * Treat out-of-memory failures as `FATAL` while reading WAL. * Fix [`pg_dump`](https://www.postgresql.org/docs/current/app-pgdump.html) to dump the new `run_as_owner` option of subscriptions. * Fix [`pg_restore`](https://www.postgresql.org/docs/current/app-pgrestore.html) so that selective restores will include both table-level and column-level ACLs for selected tables. * Add logic to [`pg_upgrade`](https://www.postgresql.org/docs/current/pgupgrade.html) to check for use of obsolete data types `abstime`, `reltime`, and `tinterval`. * Fix [`vacuumdb`](https://www.postgresql.org/docs/current/app-vacuumdb.html) to have multiple `-N` switches actually exclude tables in multiple schemas. * [`amcheck`](https://www.postgresql.org/docs/current/amcheck.html) will no longer report interrupted page
