Re: should all not-null constraints be inherited? - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: should all not-null constraints be inherited?
Date
Msg-id 20210331174037.GA344@alvherre.pgsql
Whole thread Raw
In response to Re: should all not-null constraints be inherited?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: should all not-null constraints be inherited?
Next
From: PG Bug reporting form
Date:
Subject: BUG #16951: pg_restore segfaults on custom format piped from a different version of PG