From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
Cc: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Another oddity in handling of WCO constraints in postgres_fdw |
Date: | 2017-11-01 02:16:53 |
Message-ID: | CA+TgmoYvaTKzt9K_DyXVQCtEFpLsTqAAuBte_MTPib4zae_xdA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Oct 4, 2017 at 5:58 PM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> The view with WCO is local but the modification which violates WCO is
> being made on remote server by a trigger on remote table. Trying to
> control that doesn't seem to be a good idea, just like we can't
> control what rows get inserted on the foreign server when they violate
> local constraints.
I think that's a fair point.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2017-11-01 02:19:39 | Re: PATCH: enabling parallel execution for cursors explicitly (experimental) |
Previous Message | Peter Geoghegan | 2017-11-01 01:11:29 | Re: Parallel tuplesort (for parallel B-Tree index creation) |