From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alexey Bashtanov <bashtanov@imap.cc>
Cc: pgsql-bugs@postgresql.org
Subject: Re: should all not-null constraints be inherited?
Date: Wed, 31 Mar 2021 14:40:37 -0300
Message-ID: <20210331174037.GA344@alvherre.pgsql> (raw)
In-Reply-To: <3228609.1617210121@sss.pgh.pa.us>
On 2021-Mar-31, Tom Lane wrote:
> Yeah, that's been on the to-do list for a long time. The current
> theory about it is that NOT NULL constraints ought to be represented
> as entries in pg_constraint like CHECKs are, so that the inheritance
> count and so forth could be managed the same way. We could keep
> attnotnull for convenience but it'd just mirror the existence of
> the pg_constraint entry.
>
> IIRC Alvaro had a WIP patch for this, but I've not heard anything
> about it lately.
That one is the first thing on my list for the next cycle.
--
Álvaro Herrera Valdivia, Chile
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-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, bashtanov@imap.cc
Subject: Re: should all not-null constraints be inherited?
In-Reply-To: <20210331174037.GA344@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