agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedFrom: Bruce Momjian <bruce@momjian.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Kacper Kuras <kacperkuras@hotmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: E.6.3.2.1. Constraints
Date: Tue, 22 Sep 2026 09:40:40 -0400
Message-ID: <arKFWMunv0Kzo_vm@momjian.us> (raw)
In-Reply-To: <BE714093-D030-4A1C-BCBA-EFF878248F60@yesql.se>
References: <178982939588.1243.6087398342138761960@wrigleys.postgresql.org>
<arGAwYKNjCQGpHUh@momjian.us>
<f1828bd03077c2cbde82acc220925cfa968aad4e.camel@cybertec.at>
<BE714093-D030-4A1C-BCBA-EFF878248F60@yesql.se>
On Tue, Sep 22, 2026 at 08:37:42AM +0200, Daniel Gustafsson wrote:
> > On 22 Sep 2026, at 07:51, Laurenz Albe <laurenz.albe@cybertec.at> 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 <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
view thread (5+ messages)
Message-ID: <arKFWMunv0Kzo_vm@momjian.us>
Permalink: ../arKFWMunv0Kzo_vm@momjian.us/
Also on: postgresql.org/message-id/arKFWMunv0Kzo_vm@momjian.us
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, daniel@yesql.se, laurenz.albe@cybertec.at, kacperkuras@hotmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: E.6.3.2.1. Constraints
In-Reply-To: <arKFWMunv0Kzo_vm@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox