From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 22 Feb 2026 17:22:41 +0000 (-0500)
Subject: Release notes for 18.3, 17.9, 16.13, 15.17, 14.22.
X-Git-Tag: REL_18_3~2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=24a590112cfbdac79f98472170c68b944e3a0b07;p=thirdparty%2Fpostgresql.git

Release notes for 18.3, 17.9, 16.13, 15.17, 14.22.
---

diff --git a/doc/src/sgml/release-18.sgml b/doc/src/sgml/release-18.sgml
index e952716b5eb..ebb84c43f23 100644
--- a/doc/src/sgml/release-18.sgml
+++ b/doc/src/sgml/release-18.sgml
@@ -182,6 +182,29 @@ Branch: REL_16_STABLE [ec20a4552] 2026-02-20 18:04:26 +0900
 
     <listitem>
 <!--
+Author: Álvaro Herrera <alvherre@kurilemu.de>
+Branch: master [0eeffd31b] 2026-02-21 12:22:08 +0100
+Branch: REL_18_STABLE [8d9a97e0b] 2026-02-21 12:22:08 +0100
+-->
+     <para>
+      Avoid name collisions between user-written constraints and
+      automatically-named <literal>NOT NULL</literal> constraints
+      (Laurenz Albe)
+      <ulink url="&commit_baseurl;8d9a97e0b">&sect;</ulink>
+     </para>
+
+     <para>
+      As of version 18, <literal>NOT NULL</literal> constraints have
+      full-fledged <structname>pg_constraint</structname> entries, and
+      therefore require names.  The logic for choosing a name for an
+      unnamed <literal>NOT NULL</literal> constraint failed to avoid
+      conflicts with user-written constraints elsewhere in the
+      same <command>CREATE TABLE</command> statement.
+     </para>
+    </listitem>
+
+    <listitem>
+<!--
 Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
 Branch: master [78a5e3074] 2026-02-11 18:50:57 +0200
 Branch: REL_18_STABLE [53463b4b2] 2026-02-11 18:51:06 +0200