Re: Mishandling of WCO constraints in direct foreign table modification

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp
Cc: robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Mishandling of WCO constraints in direct foreign table modification
Date: 2017-07-21 08:18:37
Message-ID: 20170721.171837.118014643.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Fri, 21 Jul 2017 12:00:03 +0900, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote in <15aa9936-9bd8-c9e3-7ca1-3948610734b4(at)lab(dot)ntt(dot)co(dot)jp>
> On 2017/07/21 3:24, Robert Haas wrote:
> > I think that's reasonable. This should be committed and back-patched
> > to 9.6, right?
>
> Yeah, because direct modify was introduced in 9.6.
>
> Attached is the second version which updated docs in postgres-fdw.sgml
> as well.

! no local joins for the query, no row-level local <literal>BEFORE</> or
! <literal>AFTER</> triggers on the target table, and no
! <literal>CHECK OPTION</> constraints from parent views.
! In <command>UPDATE</>,

Might be a silly question, is CHECK OPTION a "constraint"?

regards,

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sokolov Yura 2017-07-21 08:19:28 Re: Increase Vacuum ring buffer.
Previous Message Ashutosh Bapat 2017-07-21 07:36:17 Re: PgFDW connection invalidation by ALTER SERVER/ALTER USER MAPPING