From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
Cc: | "pgsql-hackers >> PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql document fix about showing FDW options |
Date: | 2011-08-12 03:01:14 |
Message-ID: | CA+TgmoaAyYO67xYKFy_c6ExP8_TqCC0tbPd06_rtUXAdYhKHGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2011/8/11 Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>:
> Yeah, I have (hopefully) working FDW for PostgreSQL which is based on
> the one which has been proposed for 9.1, and updates done by Heikki.
> I've implemented:
>
> * SELECT clause omitting
> * WHERE clause pushdown (assuming remote has same functions/oprators)
> * private connection caching, and VIEW which shows active connections
> * switch simple SELECT and CURSOR based on estimated # of rows,
> and FDW options to control this behavior
>
> I'd like to submit this fdw in CF 2011-09 (ASAP) for discussion of
> itself and FDW API enhancement. Please see the wiki page below for details.
Great stuff. Look forward to seeing the patch(es).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-08-12 03:22:16 | Re: index-only scans |
Previous Message | Robert Haas | 2011-08-12 02:59:55 | Re: error: could not find pg_class tuple for index 2662 |