Re: Fix bug of CHECK constraint enforceability recursion

Chao Li <li.evan.chao@gmail.com>

From: Chao Li <li.evan.chao@gmail.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: jian he <jian.universality@gmail.com>, "L. pgsql-hackers" <pgsql-hackers@lists.postgresql.org>, Andrew Dunstan <andrew@dunslane.net>
Date: 2026-05-26T07:46:46Z
Lists: pgsql-hackers

> On May 26, 2026, at 15:32, Álvaro Herrera <alvherre@kurilemu.de> wrote:
> 
> On 2026-05-26, Chao Li wrote:
>>> On May 26, 2026, at 14:05, jian he <jian.universality@gmail.com> wrote:
> 
>>> Overall, i tend to think that we should reject ALTER TABLE ALTER
>>> CONSTRAINT if it
>>> would result in the parent constraint being enforced while the child constraint
>>> is not enforced.
> 
> Yeah.
> 
>> I am not against the idea of "rejecting ALTER TABLE ALTER CONSTRAINT if 
>> it would result in the parent constraint being enforced while the child 
>> constrain is not enforced", but I’m afraid it’s too late for PG19. So, 
>> I guess we still need to fix the issue for 19, right?
> 
> I think this is a bug that we need to fix in 19 as well — I mean we should reject the ALTER TABLE.
> 
> -- 
> Álvaro Herrera

Thanks for your comment. Let me rework the patch.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/