| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | foreign table creation and NOT VALID check constraints |
| Date: | 2017-08-01 06:16:23 |
| Message-ID: | d2b7419f-4a71-cf86-cc99-bfd0f359a1ea@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2017-08-01 06:22:00 | Re: foreign table creation and NOT VALID check constraints |
| Previous Message | Victor Wagner | 2017-08-01 06:12:21 | Re: PostgreSQL 10 (latest beta) and older ICU |