On Fri, Jan 9, 2015 at 10:51 AM, Kouhei Kaigai <kai...@ak.jp.nec.com> wrote: > When custom-scan node replaced a join-plan, it shall have at least two > child plan-nodes. The callback handler of PlanCustomPath needs to be > able to call create_plan_recurse() to transform the underlying path-nodes > to plan-nodes, because this custom-scan node may take other built-in > scan or sub-join nodes as its inner/outer input. > In case of FDW, it shall kick any underlying scan relations to remote > side, thus we may not expect ForeignScan has underlying plans...
Do you have an example of this? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers