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 1x90jp-00000001h6H-2Hea for pgsql-docs@arkaria.postgresql.org; Tue, 22 Sep 2026 13:40:49 +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 1x90jo-0000000GHjg-3Si1 for pgsql-docs@arkaria.postgresql.org; Tue, 22 Sep 2026 13:40:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x90jo-0000000GHjW-2Ehi for pgsql-docs@lists.postgresql.org; Tue, 22 Sep 2026 13:40:48 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x90jj-00000000hpm-3xEC for pgsql-docs@lists.postgresql.org; Tue, 22 Sep 2026 13:40:48 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=wiRPVddlZtgfJKk0ML7xGlGgsM4SSDBkK62nWnmc0Ks=; b=Zc2Ud cQ/oWGELhAVWcAfYhQ4f4H2n1qvruVB66YXJPF0K1nwn19q92+/3ZG30KDvn8cs1woSXPIW+ocQzD GiOE23KO774H6CBwMQqY7dEpon5igXPryUoBaJS+oKnKGW61Fn6/U4io6ItAgfm6MWZtaN33BsJTq z1gDi/cYRDP1Xxs3gpX/yZu+IJKfXuJE1YrOILHQooWg6d8yPwN1etXWHQeXZOd/uVucDsoHmqVSL 7XuwBqqKOKrLgUT0Qerqbvq+/l3YNWi/XoWtOEEL78sSkbLry6im1C6PyJLm7/OsthKmSpipaoL/A JcnerFYJHcY2c2vsiLyRL5A5NLBPA==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1x90jg-00000007AIC-3jib; Tue, 22 Sep 2026 09:40:40 -0400 Date: Tue, 22 Sep 2026 09:40:40 -0400 From: Bruce Momjian To: Daniel Gustafsson Cc: Laurenz Albe , Kacper Kuras , pgsql-docs@lists.postgresql.org Subject: Re: E.6.3.2.1. Constraints Message-ID: References: <178982939588.1243.6087398342138761960@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Sep 22, 2026 at 08:37:42AM +0200, Daniel Gustafsson wrote: > > On 22 Sep 2026, at 07:51, Laurenz Albe wrote: > > > I have no right to burden committers even more, but I'd say that such changes > > should be part of the commit message. > > Not commenting on the specific commit or change here, but in general I think it > would be good if we started adding incompatibilities and upgrade notes to the > release notes over the development cycle rather than trying to collect them at > the end. It's fine to add a rough text which can be copy edited (or even > removed if deemed too minor) as the release notes process takes place, but > having it in the same commit as the change should ideally mean less work at the > end of the cycle and fewer missed notes. Actually, many committers already mark incompatibilities and mention the release notes in their commit messages. My question here is whether error code changes are incompatibilities worthy of being mentioned in the release notes, and if committers don't mention this in the commit message, how would I find them when creating the release notes? I wonder if this should be discussed on hackers instead? -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.