Re: [PG19] Three bugs with a CHECK constraint that only the child enforces

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Subject: Re: [PG19] Three bugs with a CHECK constraint that only the child enforces
Date: 2026-10-20 02:24:34
Message-ID: CAGRkXqSPNTVAe7YnmVR4brCp2+PLrR4m3MvVB0aMyaF8fFG4jA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi jian,

v4 looks good to me. One case is still lost after dump and restore,
on master and 19, and also on 18:

create table p1 (a int, constraint c check (a > 0));
create table p2 (a int, constraint c check (a > 0) not enforced);
create table k () inherits (p1, p2);
alter table k no inherit p1;

k's c is not local here, so it comes back NOT ENFORCED. I think
pg_dump still needs the ALTER CONSTRAINT ... ENFORCED from my v2-0003
for this case.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-10-20 02:31:01 Re: [PATCH] initdb: map Windows' new Canadian time zone names
Previous Message Ajin Cherian 2026-10-20 02:21:37 Re: [PG19] Sequence sync stops when the subscription owner can't SET ROLE to a sequence owner