Constraint merge and not valid status

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Constraint merge and not valid status
Date: 2016-07-13 09:22:36
Message-ID: 9ee85832-5fce-218a-c738-ccc94fc5652d@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bjørnar Ness 2016-07-13 09:49:23 UPSERT/RETURNING -> ON CONFLICT SELECT?
Previous Message Ashutosh Bapat 2016-07-13 09:00:26 Re: Oddity in handling of cached plans for FDW queries