Horton

foreign table creation and NOT VALID check constraints

Amit Langote <langote_amit_f8@lab.ntt.co.jp>

View thread View on postgr.es
From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
To: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-08-01T06:16:23Z
Lists: pgsql-hackers 
In f27a6b15e656 (9.6 & later), we decided to "Mark CHECK constraints
declared NOT VALID valid if created with table."  In retrospect,
constraints on foreign tables should have been excluded from consideration
in that commit, because the thinking behind the aforementioned commit
(that the constraint is trivially validated because the newly created
table contains no data) does not equally apply to the foreign tables case.

Should we do something about that?

Thanks,
Amit

Commits

  1. Allow a foreign table CHECK constraint to be initially NOT VALID.

  2. Mark CHECK constraints declared NOT VALID valid if created with table.