On Thu, Feb 24, 2011 at 9:06 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, Feb 24, 2011 at 8:13 AM, Shigeru HANADA
> <hanada@metrosystems.co.jp> wrote:
>>
>> On Wed, 23 Feb 2011 20:30:05 +0900
>> Shigeru HANADA <hanada@metrosystems.co.jp> wrote:
>>
>>>
>>> On Tue, 22 Feb 2011 11:33:25 -0500
>>> Robert Haas <robertmhaas@gmail.com> wrote:
>>> > Is anyone actually working on a new version of this patch sufficiently
>>> > rapidly that we can expect a new version in the next day or two?
>>> >
>>> > If not, I think we mark this one Returned with Feedback and revisit it for 9.2.
>>>
>>> I'm working on it.
>>>
>>> Fixes for new FDW API have been done, but there are some problems in
>>> SQL generation codes, such as SELECT clause optimization (omitting
>>> unused column from SELECT clause). It would take a while, but I'll
>>> post revised version of the patch tomorrow.
>>
>> Attached is a revised version of postgresql_fdw patch. I started from
>> Heikki's latest patch, and modified some points:
>>
>> 1) use new FDW API
>> 2) use EXTENSION framework
>> 3) SELECT clause optimization (use NULL for unused columns)
>> 4) show remote query in EXPLAIN output
>>
>> WHERE clause pushdown was implemented in Heikki's version, so I didn't
>> touch around it. Now I'm working on cost estimation and connection
>> management, but they would need some more work.
>
> So this is still work-in-progress? When do you expect a final version?
Since it sounds like this still needs more work, I'm going to mark it
Returned with Feedback. I hope we integrate this during the 9.2
cycle.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
