| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: foreign table creation and NOT VALID check constraints |
| Date: | 2017-08-01 06:22:00 |
| Message-ID: | CANP8+jL=bbS6cZRc28=AE2_WwQH=K+mg0zzBennFjEiXsyuTtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1 August 2017 at 07:16, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> 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?
In what way does it not apply? Do you have a failure case?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yugo Nagata | 2017-08-01 06:28:15 | A little improvementof ApplyLauncherMain loop code |
| Previous Message | Amit Langote | 2017-08-01 06:16:23 | foreign table creation and NOT VALID check constraints |