Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x8FLe-000000013PC-2MP7 for pgsql-docs@arkaria.postgresql.org; Sun, 20 Sep 2026 11:04:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x8FLc-00000006Jj9-2Bud for pgsql-docs@arkaria.postgresql.org; Sun, 20 Sep 2026 11:04:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x7wOF-00000005EZ3-1nE5 for pgsql-docs@lists.postgresql.org; Sat, 19 Sep 2026 14:50:07 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x7wOC-00000000D63-3Au7 for pgsql-docs@lists.postgresql.org; Sat, 19 Sep 2026 14:50:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=0KXzUGMgD2qcZLXBftA2T84Fx8wtEE2UyvCFXeVJjWU=; b=IvL92luGuzXJ4vQKeAtb9Xxawm bGBD3krezEGNPX07c+igfgLZ3pYXbrsmsan8ZoHWSA6Ffj+wK+UvsHBTyoKdFCFu0WphjCmw9ZALA DEL+P8MJI8AX9xntg4Bo6/QFZhD+c9d9GOTZoxXAHHXKyAU4UeQXkNEqDn7xKvX0oElQbLF3Lw1CY iZywFcVHbbldhApwh+2m5lGX87iVVRNE9IE+XltcgzG0FrTCw72Jpa9/mFSqj4lvIQVJgt48Mm6Qe 6dNsABm9t7yHUn1gxV8meX4848PwfvA/qaHkZJ0zPzjPAM3lfPc+pneMNv+ANLCMordYWWSDYLkm4 eoTHX0Eg==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x7wOC-000aM4-0X for pgsql-docs@lists.postgresql.org; Sat, 19 Sep 2026 14:50:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x7wOA-00000001maJ-2TaP for pgsql-docs@lists.postgresql.org; Sat, 19 Sep 2026 14:50:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: E.6.3.2.1. Constraints To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: kacperkuras@hotmail.com Reply-To: kacperkuras@hotmail.com, pgsql-docs@lists.postgresql.org Date: Sat, 19 Sep 2026 14:49:55 +0000 Message-ID: <178982939588.1243.6087398342138761960@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/release-18.html Description: Commit 086c84b23 changed what a foreign key with ON DELETE RESTRICT or ON UPDATE RESTRICT raises when it refuses a change: SQLSTATE 23001 (restrict_violation) instead of 23503 (foreign_key_violation), and the message now says "violates RESTRICT setting of foreign key constraint". The PostgreSQL 18 release notes do not mention it. Code that catches 23503 to report that a row is still referenced stops matching RESTRICT keys after upgrading, while NO ACTION keys still raise 23503. The same notes list the change to the XML error codes (cd838e200), so this one seems to belong there as well.