Re: PostgreSQL FDW update

From: Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>
To: Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL FDW update
Date: 2011-02-24 13:13:15
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Wed, 23 Feb 2011 20:30:05 +0900
Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp> wrote:

> On Tue, 22 Feb 2011 11:33:25 -0500
> Robert Haas <robertmhaas(at)gmail(dot)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.

Shigeru Hanada

Attachment Content-Type Size
20110224-postgresql_fdw.patch application/octet-stream 48.5 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Urbański 2011-02-24 14:03:45 Re: pl/python tracebacks
Previous Message Peter Eisentraut 2011-02-24 13:10:01 Re: pl/python tracebacks