Re: WIP: Join push-down for foreign tables - Mailing list pgsql-hackers

From Kohei KaiGai
Subject Re: WIP: Join push-down for foreign tables
Date
Msg-id CADyhKSVkZ9zTV0n2Yx2P4Ojh5LOqL_9R4WsEuU=sy2hLxGX6Xg@mail.gmail.com
Whole thread Raw
In response to Re: WIP: Join push-down for foreign tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP: Join push-down for foreign tables
List pgsql-hackers
How about the current status of this patch, although it is still
"Waiting on author".

If Hanada-san would propose contrib/pgsql_fdw as a basis of join-pushdown
feature, I'll likely volunteer to review the patch.
I'm also interested in this feature. Hopefully, I'd like to try other
kind of pushing
down (such as aggregate, sort, ...) or updatable foreign tables. :-)

Thanks,

2011/10/10 Tom Lane <tgl@sss.pgh.pa.us>:
> Robert Haas <robertmhaas@gmail.com> writes:
>> This might be out of left field, but wouldn't it make more sense to
>> get postgresql_fdw committed first, and then add the join push-down
>> functionality afterwards?  I mean, otherwise, we're going to be left
>> with a situation where we have join pushdown in core, but the only FDW
>> that can actually make use of it elsewhere.
>
> There's likely to be a lot of FDW infrastructure that will not be
> exercised by anything in core or contrib ...
>
>                        regards, tom lane
>



--
KaiGai Kohei <kaigai@kaigai.gr.jp>


pgsql-hackers by date:

Previous
From: Phil Sorber
Date:
Subject: Re: pg_dumpall Sets Roll default_tablespace Before Creating Tablespaces
Next
From: Tom Lane
Date:
Subject: Synchronized snapshots versus multiple databases