From: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
---|---|
To: | Jasmin Dizdarevic <jasmin(dot)dizdarevic(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: FOREIGN TABLE with dblink |
Date: | 2011-06-29 02:08:28 |
Message-ID: | 4E0A891C.5080500@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Jasmin,
(2011/06/16 19:40), Jasmin Dizdarevic wrote:
> Hi,
>
> is there any way to use the new foreign table feature with dblink?
> That's almost clear to me:
>
> CREATE FOREIGN DATA WRAPPER pgsql90;
>
> CREATE SERVER srvlocal90 FOREIGN DATA WRAPPER pgsql90 OPTIONS (hostaddr
> '127.0.0.1', dbname 'lotty');
>
> CREATE USER MAPPING FOR pgsql SERVER srvlocal90 OPTIONS (user 'pgsql',
> password '');
>
> I would like to replace this
>
> SELECT dblink_connect('myconn', 'srvlocal90');
> SELECT * FROM dblink('myconn', 'select * from mytests.fttest') AS t(id int,
> myname text);
>
> to something like this:
>
> CREATE FOREIGN TABLE mytests.lnkto90_fttest (
> id int,
> myname text
> )
> SERVER srvlocal90 OPTIONS (????)
>
> SELECT * FROM mytests.lnkto90_fttest;
Your assumption is exactly what the foreign table feature aims at;
foreign table feature would allow you to access external data via a SQL
statement which conformed with the SQL statement, though foreign tables
are read-only in the first release.
But unfortunately FDW for PostgreSQL won't be shipped with 9.1 release.
Hopefully, PostgreSQL-FDW for 9.1 might be released as an external
module, and then you would be able to replace dblink with foreign tables.
Regards,
--
Shigeru Hanada
From | Date | Subject | |
---|---|---|---|
Next Message | Ben Carbery | 2011-06-29 02:10:32 | Re: PL/PGSQL - dynamic variable names |
Previous Message | Ben Carbery | 2011-06-29 01:41:19 | Re: PL/PGSQL - dynamic variable names |