<div dir="ltr"><br /><div class="gmail_extra"><br /><div class="gmail_quote"><span class=""></span><br /><span
class=""></span><br /><span class=""></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px
#cccsolid;padding-left:1ex"><span class=""> I wrote:<br /><blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px#ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px#ccc solid;padding-left:1ex"> Probably something like this:<br /><br /> Foreign Processing<br />
Remote Operations: ...<br /><br /> In the Remote Operations line, the FDW/extension could print any info<br />
aboutremote operations, eg, "Scan/Join + Aggregate".<br /></blockquote></blockquote><br /></span><span
class=""><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
"Foreign"implies this node is processed by FDW, but "Procesing" gives us<br /> no extra information; seems to me
redundant.<br/></blockquote><br /></span> I intentionally chose that word and thought we could leave detailed
descriptionsabout remote operations to the FDW/extension; a broader word like "Processing" seems to work well because
weallow various kinds of operations to the remote side, in addition to scans/joins, to be performed in that one Foreign
Scannode indicated by "Foreign Processing", such as aggregation, window functions, distinct, order by, row locking,
tablemodification, or combinations of them.<span class=""><br /></span><br clear="all" /></blockquote></div>"Scan" is a
betterword than "Processing". From plan's perspective it's ultimately a Scan (on the data produced by the foreign
server)and not processing.<br /></div><div class="gmail_extra">-- <br /><div class="gmail_signature"
data-smartmail="gmail_signature"><divdir="ltr">Best Wishes,<br />Ashutosh Bapat<br />EnterpriseDB Corporation<br />The
PostgresDatabase Company<br /></div></div></div></div>