Re: cataloguing NOT NULL constraints - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: cataloguing NOT NULL constraints
Date
Msg-id 1b70dca9-117e-4176-83b3-b9859d7fa692@eisentraut.org
Whole thread Raw
In response to Re: cataloguing NOT NULL constraints  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On 15.05.24 09:50, Alvaro Herrera wrote:
> 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

I'm confused that these were kept.  The first one was specifically to 
make the catalog representation of domain not-null constraints 
consistent with table not-null constraints.  But the table part was 
reverted, so now the domain constraints are inconsistent again.

The second one refers to the first one, but it might also fix some 
additional older issue, so it would need more investigation.




pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: in parentesis is not usual on DOCs
Next
From: Melanie Plageman
Date:
Subject: Re: First draft of PG 17 release notes