Re: Oddity in EXPLAIN for foreign/custom join pushdown plans - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: Oddity in EXPLAIN for foreign/custom join pushdown plans
Date
Msg-id CAFjFpRe3gUqy8oVNiCrRM6xAN2X1xN6uc51jP0EBUgKbwkiODA@mail.gmail.com
Whole thread
In response to Re: Oddity in EXPLAIN for foreign/custom join pushdown plans  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
Responses Re: Oddity in EXPLAIN for foreign/custom join pushdown plans
List pgsql-hackers




I wrote:
Probably something like this:

   Foreign Processing
     Remote Operations: ...

In the Remote Operations line, the FDW/extension could print any info
about remote operations, eg, "Scan/Join + Aggregate".

"Foreign" implies this node is processed by FDW, but "Procesing" gives us
no extra information; seems to me redundant.

I intentionally chose that word and thought we could leave detailed descriptions about remote operations to the FDW/extension; a broader word like "Processing" seems to work well because we allow various kinds of operations to the remote side, in addition to scans/joins, to be performed in that one Foreign Scan node indicated by "Foreign Processing", such as aggregation, window functions, distinct, order by, row locking, table modification, or combinations of them.

"Scan" is a better word than "Processing". From plan's perspective it's ultimately a Scan (on the data produced by the foreign server) and not processing.
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Oddity in EXPLAIN for foreign/custom join pushdown plans
Next
From: Kouhei Kaigai
Date:
Subject: Re: Oddity in EXPLAIN for foreign/custom join pushdown plans