From: | Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp> |
---|---|
To: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SQL/MED - core functionality |
Date: | 2010-12-01 05:53:01 |
Message-ID: | 20101201145300.2BA6.6989961C@metrosystems.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 1 Dec 2010 12:30:46 +0900
Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> wrote:
> This is another topic, but it would be useful if CREATE FOREIGN TABLE
> can omit column definitions since fdw usually knows what should be
> there in the definitions. I some times mistyped the column names
> between remote and local and resulted in fail on execution.
The SQL/MED standard includes "IMPORT FOREIGN SCHEMA schema FROM
SERVER server" syntax which imports definitions of remote tables in
the specified schema into local PostgreSQL, and you can optionally specify
the list of target tables with "LIMIT TO table_list" option.
This syntax would make defining foreign tables easier, but it needs to
enhance both FDW API and core parser.
Regards,
--
Shigeru Hanada
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-12-01 06:03:26 | Idle git question: how come so many "objects"? |
Previous Message | Tom Lane | 2010-12-01 05:31:34 | Re: We really ought to do something about O_DIRECT and data=journalled on ext4 |