Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)

From: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thom Brown <thom(at)linux(dot)com>, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>
Subject: Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)
Date: 2016-01-19 07:33:58
Message-ID: 569DE6E6.3000001@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016/01/18 19:46, Ashutosh Bapat wrote:
> PFA patches for postgres_fdw join pushdown, taken care of all TODOs in
> my last mail.
>
> Here is the list of things that have been improved/added new as compared
> to Hanada-san's previous patch at [1].

Great! Thank you for working on that! I'll review the patch.

> I will be working next on (in that order)
> 1. eval_plan_qual fix for foreign join. (Considered as a must-have for 9.6)
> 2. Pushing down ORDER BY clause along with join pushdown
> 3. Parameterization of foreign join paths (Given the complexity of the
> feature this may not make it into 9.6)

As discussed internally, I think #3 might have some impact on the
overall design of the EvalPlanQual fix, especially the design of a
helper function that creates a local join execution path for a foreign
join path for EvalPlanQual. So, IMO, I think the order is #1, #3, and
#2 (or #3, #1, #2).

Best regards,
Etsuro Fujita

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2016-01-19 08:06:56 Re: Proposal: Trigonometric functions in degrees
Previous Message Tomas Vondra 2016-01-19 07:20:41 Re: silent data loss with ext4 / all current versions