Re: [HACKERS] Another oddity in handling of WCO constraints in postgres_fdw
От | Ashutosh Bapat |
---|---|
Тема | Re: [HACKERS] Another oddity in handling of WCO constraints in postgres_fdw |
Дата | |
Msg-id | CAFjFpRfCQ-6a-FXM-d9FhDzx4Bh0b6EKvbad8ypLV-spPqWFDQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Another oddity in handling of WCO constraints in postgres_fdw (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>) |
Ответы |
Re: [HACKERS] Another oddity in handling of WCO constraints inpostgres_fdw
|
Список | 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
В списке pgsql-hackers по дате отправления: