Hi Dinesh, I tested the latest v6 patch. I set up two PostgreSQL instances (one local and one remote) connected through postgres_fdw, created a foreign table, and verified the behavior before and after applying the patch. Before applying the patch, EXPLAIN on the foreign table only displayed a Foreign Scan node. EXPLAIN (VERBOSE) showed the generated Remote SQL, but it did not provide any information about how the remote PostgreSQL server planned to execute the query.
After applying the patch, rebuilding PostgreSQL, and restarting both instances, I verified that EXPLAIN (REMOTE_PLANS) now displays a new Remote Plans section. The output correctly included the execution plan generated by the remote PostgreSQL server (for example, Seq Scan on emp) along with the corresponding Plan Node ID. I also verified the following: EXPLAIN (REMOTE_PLANS) successfully displays the remote execution plan. EXPLAIN (REMOTE_PLANS) with a WHERE clause correctly reflects the filter condition in the remote plan. EXPLAIN (REMOTE_PLANS, VERBOSE) continues to display the existing Remote SQL output together with the new Remote Plans section. EXPLAIN (REMOTE_PLANS, ANALYZE) correctly reports: ERROR: EXPLAIN options REMOTE_PLANS and ANALYZE cannot be used together which matches the current implementation. I did not encounter any issues during my testing, and the feature behaved as expected in the scenarios I tested. Thanks for working on this feature. Regards, solai
