Re: foreign table creation and NOT VALID check constraints

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: foreign table creation and NOT VALID check constraints
Date: 2017-08-02 11:40:30
Message-ID: CA+TgmoZr8W6PAgPKtiLx1Soi7RZ0U+Lc2zxgiveurcHLm+Le9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 2, 2017 at 3:46 AM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> If the user has specified "not valid" for a constraint on the foreign
> table, there is high chance that s/he is aware of the fact that the
> remote table that the foreign table points to has some rows which will
> violet the constraint. So, +1.

+1 from me, too.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Kuzmenkov 2017-08-02 12:00:27 Re: Proposal for CSN based snapshots
Previous Message Robert Haas 2017-08-02 11:35:14 Re: A bug in mapping attributes in ATExecAttachPartition()