Re: Missing importing option of postgres_fdw - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Missing importing option of postgres_fdw
Date
Msg-id CA+TgmoYgm5gNiAby-fJrJ60HKLSBU0F_7fuFjFNq7CNs8PGgqA@mail.gmail.com
Whole thread Raw
In response to Re: Missing importing option of postgres_fdw  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Missing importing option of postgres_fdw
List pgsql-hackers
On Mon, Apr 27, 2015 at 7:47 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Authorizing ALTER FOREIGN TABLE as query string that a FDW can use
> with IMPORT FOREIGN SCHEMA is a different feature than what is
> proposed in this patch, aka an option for postgres_fdw and meritates a
> discussion on its own because it impacts all the FDWs and not only
> postgres_fdw. Now, related to this patch, we could live without
> authorizing ALTER FOREIGN TABLE because CREATE FOREIGN TABLE does
> authorize the definition of CHECK constraints.

I agree.  I don't think there's a huge problem with allowing IMPORT
FOREIGN SCHEMA to return ALTER FOREIGN TABLE statements, but it
doesn't really seem to be necessary.  I don't see why we can't just
declare the CHECK constraints in the CREATE FOREIGN TABLE statement
instead of adding more DDL.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Can pg_dump make use of CURRENT/SESSION_USER
Next
From: Robert Haas
Date:
Subject: Re: forward vs backward slashes in msvc build code