From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Missing importing option of postgres_fdw |
Date: | 2015-04-27 07:20:33 |
Message-ID: | 553DE341.2080006@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015/04/27 15:51, Michael Paquier wrote:
> On Mon, Apr 27, 2015 at 3:15 PM, Etsuro Fujita
> <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> I noticed that there is no postgres_fdw option to control whether check
>> constraints on remote tables are included in the definitions of foreign
>> tables imported from a remote PG server when performing IMPORT FOREIGN
>> SCHEMA, while we now allow check constraints on foreign tables.
> I guess that the addition of this option makes sense, but I think that
> this patch is doing it wrong by using ALTER FOREIGN TABLE and by
> changing the queries authorized in ImportForeignSchema(). The point of
> IMPORT FOREIGN SCHEMA is to authorize only CREATE FOREIGN TABLE and
> not other types of queries, not to mention that CREATE FOREIGN TABLE
> supports the definitions of constraints at table and column-level.
I don't think so. IMO, I think it'd be more convenient and flexible to
allow ALTER FOREIGN TABLE for creating foreign table definitions during
ImportForeignSchema().
Thanks for the comment!
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Shigeru HANADA | 2015-04-27 09:05:44 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |
Previous Message | Michael Paquier | 2015-04-27 06:51:46 | Re: Missing importing option of postgres_fdw |