Horton

Re: CHECK Constraint Deferrable

Vik Fearing <vik@postgresfriends.org>

View thread View on postgr.es
From: Vik Fearing <vik@postgresfriends.org>
To: Robert Haas <robertmhaas@gmail.com>, "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Andreas Joseph Krogh <andreas@visena.com>, Dilip Kumar <dilipbalaut@gmail.com>, Himanshu Upadhyaya <upadhyaya.himanshu@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: 2023-10-13T00:36:02Z
Lists: pgsql-hackers 
On 10/10/23 15:12, Robert Haas wrote:
> On Mon, Oct 9, 2023 at 5:07 PM David G. Johnston
> <david.g.johnston@gmail.com> wrote:
>>> 2. I don't think it's a good idea for the same patch to try to solve
>>> two problems unless they are so closely related that solving one
>>> without solving the other is not sensible.
>>
>> A NOT NULL constraint apparently is just a special case of a check constraint which seems closely related enough to match your definition.
> 
> Yes, that might be true. I suppose I'd like to hear from the patch
> author(s) about that. I'm somewhat coming around to your idea that
> maybe both should be covered together, but I'm not the one writing the
> patch.

Álvaro Herrera has put (and is still putting) immense effort into 
turning NOT NULL into a CHECK constraint.

Honestly, I don't see why the two patches need to be combined.
-- 
Vik Fearing