Re: Missing importing option of postgres_fdw

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: 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
Date: 2015-05-15 18:32:50
Message-ID: CA+TgmoZFV13BfDJzAF11qb7cxyNYdD6QVTAPrv7qvMLRcStWnA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 14, 2015 at 6:37 AM, Etsuro Fujita
<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> On second thought, I noticed that as for this option, we cannot live without
> allowing IMPORT FOREIGN SCHEMA to return ALTER FOREIGN TABLE statements
> because we cannot declare the convalidated information in the CREATE FOREIGN
> TABLE statement. So, I think we shoould also allow it to return ALTER
> FOREIGN TABLE statements. Am I right?

Isn't convalidated utterly meaningless for constraints on foreign tables?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-05-15 18:46:21 Re: Minor improvement to create_foreign_table.sgml
Previous Message Robert Haas 2015-05-15 18:30:02 Re: PATCH: adaptive ndistinct estimator v4