|From:||Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Missing importing option of postgres_fdw|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 2015/05/26 3:15, Tom Lane wrote:
> Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)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.
|Next Message||Josh Berkus||2015-05-26 03:52:58||fsync bug faq for publication?|
|Previous Message||Andres Freund||2015-05-26 03:05:51||Re: anole: assorted stability problems|