| From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Another oddity in handling of WCO constraints in postgres_fdw |
| Date: | 2018-03-12 07:55:03 |
| Message-ID: | 5AA63257.5010805@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
(2018/03/09 20:55), Etsuro Fujita wrote:
> (2018/03/08 14:24), Ashutosh Bapat wrote:
>> For local constraints to be enforced, we use remote
>> constraints. For local WCO we need to use remote WCO. That means we
>> create many foreign tables pointing to same local table on the foreign
>> server through many views, but it's not impossible.
>
> Maybe I don't understand this correctly, but I guess that it would be
> the user's responsibility to not create foreign tables in such a way.
I think I misunderstood your words. Sorry for that. I think what you
proposed would be a solution for this issue, but I'm not sure that's a
good one because that wouldn't work for the data sources that don't
support views with WCO options.
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeevan Ladhe | 2018-03-12 08:07:21 | Fix error in ECPG while connection handling |
| Previous Message | Michael Paquier | 2018-03-12 07:28:56 | Re: PATCH: Configurable file mode mask |