From: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP: Join push-down for foreign tables |
Date: | 2011-10-21 14:53:33 |
Message-ID: | CADyhKSVkZ9zTV0n2Yx2P4Ojh5LOqL_9R4WsEuU=sy2hLxGX6Xg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us>:
> Robert Haas <robertmhaas(at)gmail(dot)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(at)kaigai(dot)gr(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-10-21 15:36:37 | Synchronized snapshots versus multiple databases |
Previous Message | Robert Haas | 2011-10-21 14:47:46 | Re: [v9.2] Fix Leaky View Problem |