Re: Oddity in EXPLAIN for foreign/custom join pushdown plans

From: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Oddity in EXPLAIN for foreign/custom join pushdown plans
Date: 2016-08-02 05:45:23
Message-ID: 992f1cff-d350-6b49-75ad-828c835b0eae@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016/08/02 13:32, Kouhei Kaigai wrote:

I wrote:
>> My concern here is EXPLAIN for foreign joins. I think it's another
>> problem how we handle Foreign Scan plan nodes representing
>> post-scan/join operations in EXPLAIN, so I'd like to leave that for
>> another patch.

> What is the post-scan/join operations? Are you saying EPQ recheck and
> alternative local join plan?

No. I mean e.g., aggregation, window functions, sorting, or table
modification. In other words, Foreign Scan plan nodes created from
ForeignPath paths created from GetForeignUpperPaths.

Best regards,
Etsuro Fujita

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2016-08-02 05:49:09 Re: Reviewing freeze map code
Previous Message Kyotaro HORIGUCHI 2016-08-02 05:42:35 Re: Wrong defeinition of pq_putmessage_noblock since 9.5