Re: [HACKERS] Another oddity in handling of WCO constraints in postgres_fdw
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
From: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
To: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Cc: Stephen Frost <sfrost@snowman.net>,
Arthur Zakirov <a.zakirov@postgrespro.ru>, Robert Haas <robertmhaas@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2018-03-13T04:11:15Z
Lists: pgsql-hackers
On Mon, Mar 12, 2018 at 1:25 PM, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> wrote: > (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. Our solution for the constraints doesn't work with the data sources (like flat files) which don't support constraints. So, that argument doesn't help. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
Commits
-
Fix WITH CHECK OPTION on views referencing postgres_fdw tables.
- a45adc747e27 12.0 landed
-
Allow insert and update tuple routing and COPY for foreign tables.
- 3d956d9562aa 11.0 cited
-
When WCOs are present, disable direct foreign table modification.
- 7086be6e3627 10.0 cited