Re: Missing importing option of postgres_fdw
| От | Etsuro Fujita |
|---|---|
| Тема | Re: Missing importing option of postgres_fdw |
| Дата | |
| Msg-id | 5563E4BA.5090405@lab.ntt.co.jp обсуждение исходный текст |
| Ответ на | Re: Missing importing option of postgres_fdw (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
On 2015/05/26 3:15, Tom Lane wrote: > Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> writes: >> On 2015/05/22 23:50, Tom Lane wrote: >>> So I think worrying about convalidated is pretty pointless. Really, >>> it is up to the user to determine what constraints should be attached >>> to the foreign table, and IMPORT FOREIGN SCHEMA can't help much. > >> Agreed. So, I'd like to propose to update the docs as above. Please >> find attached a patch. The existing sentence "Checking other types of >> constraints is always left to the remote server." sounds to me that >> constraints on foreign tables are enforced locally when updating the >> foreign tables. So, I'd also like to propose to remove that sentence. >> Maybe I'm missing something though. > > Yeah, I agree this documentation is inadequate; but I think it'd be a good > thing to spell out the reason why there's no support for importing check > constraints. I committed the attached enlarged version. Thanks! Best regards, Etsuro Fujita
В списке pgsql-hackers по дате отправления: