From 272aecfc2f496c90ddcba8e69b0f9b5cf2978ec6 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 4 Feb 2024 14:17:14 -0500 Subject: [PATCH] Release notes for 16.2, 15.6, 14.11, 13.14, 12.18. --- doc/src/sgml/release-16.sgml | 78 +++++++++++++++--------------------- 1 file changed, 32 insertions(+), 46 deletions(-) diff --git a/doc/src/sgml/release-16.sgml b/doc/src/sgml/release-16.sgml index 21387e3424..a380b7d4fa 100644 --- a/doc/src/sgml/release-16.sgml +++ b/doc/src/sgml/release-16.sgml @@ -23,7 +23,13 @@ - However, if you are upgrading from a version earlier than 16.1, + However, one bug was fixed that could have resulted in corruption of + GIN indexes during concurrent updates. If you suspect such + corruption, reindex affected indexes after installing this update. + + + + Also, if you are upgrading from a version earlier than 16.1, see . @@ -58,25 +64,6 @@ Branch: REL_12_STABLE [c922b2410] 2023-12-11 12:02:01 +0100 - - When dequeueing from an LWLock, avoid needing to search the list of - waiting processes (Andres Freund) - - - - This fixes O(N^2) behavior when the list of waiters is long. In - some use-cases this results in substantial throughput improvements. - - - - - - Add more interlocks between CREATE DATABASE and - base backup (Noah Misch) + Ensure durability of CREATE DATABASE (Noah Misch) - This fixes some cases where a base backup taken concurrently - with CREATE DATABASE could produce a corrupt - image of the new database. + If an operating system crash occurred during or shortly + after CREATE DATABASE, recovery could fail, or + subsequent connections to the new database could fail. If a base + backup was taken in that window, similar problems could be observed + when trying to use the backup. The symptom would be that the + database directory, PG_VERSION file, or + pg_filenode.map file was missing or empty. @@ -909,27 +899,6 @@ Branch: REL_15_STABLE [57aae65ae] 2023-11-22 11:14:35 +0530 - - Prevent examining system catalogs with the wrong snapshot during - logical decoding (Fei Changhong) - - - - If decoding begins partway through a transaction that modifies - system catalogs, the decoder may not recognize that, causing it to - fail to treat that transaction as in-progress for catalog lookups. - This fix deals with the case that a top-level transaction is already - marked as containing catalog changes, but its subtransaction(s) are - not. - - - - - + + Report ENOMEM errors from file-related system + calls as ERRCODE_OUT_OF_MEMORY, + not ERRCODE_INTERNAL_ERROR (Alexander Kuzmenkov) + + + + +