Constraint merge and not valid status - Mailing list pgsql-hackers

From Amit Langote
Subject Constraint merge and not valid status
Date
Msg-id 9ee85832-5fce-218a-c738-ccc94fc5652d@lab.ntt.co.jp
Whole thread Raw
Responses Re: Constraint merge and not valid status  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Re: Constraint merge and not valid status  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

Consider a scenario where one adds a *valid* constraint on a inheritance
parent which is then merged with a child table's *not valid* constraint
during inheritance recursion.  If merged, the constraint is not checked
for the child data even though it may have some.  Is that an oversight?

Thanks,
Amit





pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Oddity in handling of cached plans for FDW queries
Next
From: Amit Kapila
Date:
Subject: Re: Simplifying the interface of UpdateMinRecoveryPoint