From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Bruce Momjian <bruce@momjian.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: exclusion@gmail.com, dean.a.rasheed@gmail.com, andrewbille@gmail.com, peter@eisentraut.org, pgsql-hackers@lists.postgresql.org, Justin Pryzby <pryzby@telsasoft.com>
Subject: Re: cataloguing NOT NULL constraints
Date: Wed, 15 May 2024 09:50:36 +0200
Message-ID: <202405150750.qq723smkwrqc@alvherre.pgsql> (raw)
In-Reply-To: <ZkQQwUhTZd2oeuav@momjian.us>
On 2024-May-14, Bruce Momjian wrote:
> Turns out these commits generated a single release note item, which I
> have now removed with the attached committed patch.
Hmm, but the commits about not-null constraints for domains were not
reverted, only the ones for constraints on relations. I think the
release notes don't properly address the ones on domains. I think it's
at least these two commits:
> -Author: Peter Eisentraut <peter@eisentraut.org>
> -2024-03-20 [e5da0fe3c] Catalog domain not-null constraints
> -Author: Peter Eisentraut <peter@eisentraut.org>
> -2024-04-15 [9895b35cb] Fix ALTER DOMAIN NOT NULL syntax
It may still be a good idea to make a note about those, at least to
point out that information_schema now lists them. For example, pg11
release notes had this item
<!--
2018-02-07 [32ff26911] Add more information_schema columns
-->
<para>
Add <literal>information_schema</literal> columns related to table
constraints and triggers (Peter Eisentraut)
</para>
<para>
Specifically,
<structname>triggers</structname>.<structfield>action_order</structfield>,
<structname>triggers</structname>.<structfield>action_reference_old_table</structfield>,
and
<structname>triggers</structname>.<structfield>action_reference_new_table</structfield>
are now populated, where before they were always null. Also,
<structname>table_constraints</structname>.<structfield>enforced</structfield>
now exists but is not yet usefully populated.
</para>
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
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-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, bruce@momjian.us, robertmhaas@gmail.com, horikyota.ntt@gmail.com, pryzby@telsasoft.com
Subject: Re: cataloguing NOT NULL constraints
In-Reply-To: <202405150750.qq723smkwrqc@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox