public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dominique Devienne <[email protected]>
To: [email protected]
Subject: Re: pg_constraint catalog changes in v18 beta1???
Date: Wed, 4 Jun 2025 15:43:30 +0200
Message-ID: <CAFCRh--hgwsVFz6f3HTWDde=h2gjW6MrnFJFAbNEOGkm5vqDqQ@mail.gmail.com> (raw)
In-Reply-To: <CAFCRh--+c38Qfp_i4SOt65PKuKcZLZAtS+1P=6BjMAnoNHisGw@mail.gmail.com>
References: <CAFCRh--+c38Qfp_i4SOt65PKuKcZLZAtS+1P=6BjMAnoNHisGw@mail.gmail.com>

On Wed, Jun 4, 2025 at 3:07 PM Dominique Devienne <[email protected]> wrote:
> Is this change of behavior normal?
> ... Was this intentional?

Well, apparently it is intentional, I found an entry in the release notes.
Case closed I guess. I adapted our introspection. Thanks, --DD

From https://www.postgresql.org/docs/18/release-18.html#RELEASE-18-CONSTRAINTS:
Store column NOT NULL specifications in pg_constraint (Álvaro Herrera,
Bernd Helmle) §
This allows names to be specified for NOT NULL constraint. This also
adds NOT NULL constraints to foreign tables and NOT NULL inheritance
control to local tables.

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: [email protected]
  Cc: [email protected]
  Subject: Re: pg_constraint catalog changes in v18 beta1???
  In-Reply-To: <CAFCRh--hgwsVFz6f3HTWDde=h2gjW6MrnFJFAbNEOGkm5vqDqQ@mail.gmail.com>

* 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