From: Tom Lane Date: Sun, 4 May 2025 17:52:59 +0000 (-0400) Subject: Release notes for 17.5, 16.9, 15.13, 14.18, 13.21. X-Git-Tag: REL_17_5~5 X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=09fac4a28daa49af91d2af28348267efe916c95b;p=postgresql.git Release notes for 17.5, 16.9, 15.13, 14.18, 13.21. --- diff --git a/doc/src/sgml/release-17.sgml b/doc/src/sgml/release-17.sgml index cf6d678a8d4..fdb5205a2bf 100644 --- a/doc/src/sgml/release-17.sgml +++ b/doc/src/sgml/release-17.sgml @@ -23,8 +23,15 @@ - However, if you have any BRIN bloom indexes, it may be advisable to - reindex them after updating. See the first changelog entry below. + However, if you have any self-referential foreign key constraints on + partitioned tables, it may be necessary to recreate those constraints + to ensure that they are being enforced correctly. See the first + changelog entry below. + + + + Also, if you have any BRIN bloom indexes, it may be advisable to + reindex them after updating. See the second changelog entry below. @@ -40,6 +47,39 @@ + + Handle self-referential foreign keys on partitioned tables correctly + (Álvaro Herrera) + § + + + + Creating or attaching partitions failed to make the required catalog + entries for a foreign-key constraint, if the table referenced by the + constraint was the same partitioned table. This resulted in failure + to enforce the constraint fully. + + + + To fix this, you should drop and recreate any self-referential + foreign keys on partitioned tables, if partitions have been created + or attached since the constraint was created. Bear in mind that + violating rows might already be present, in which case recreating + the constraint will fail, and you'll need to fix up those rows + before trying again. + + + + + Fix ALTER TABLE ADD COLUMN to correctly handle - the case of a domain type that has a default (Tom Lane, Tender Wang) + the case of a domain type that has a default + (Jian He, Tom Lane, Tender Wang) § § @@ -694,38 +735,6 @@ Branch: REL_17_STABLE [727bc6ac3] 2025-02-19 10:04:44 +0900 - - Skip WAL recycling and preallocation during archive recovery, to - avoid corruption of WAL files that were restored from the archive - (Noah Misch, Arun Thirupathi) - - - - This change back-patches v15-era fixes that were considered largely - cosmetic at the time, but turn out to prevent data corruption in the - wake of subsequent fixes. - - - - - - - Fix assertion failure in snapshot building (Masahiko Sawada) - - - - - - - Allow contrib/dblink queries to be interrupted - by query cancel (Noah Misch) - - - - This change back-patches a v17-era fix. It prevents possible hangs - in CREATE DATABASE and DROP - DATABASE due to failure to detect deadlocks. - - - - -