Shigeru Hanada <shigeru.han...@gmail.com> writes: > (2012/02/14 17:40), Etsuro Fujita wrote: >> As discussed at >> that thread, it would have to change the PlanForeignScan API to let the >> FDW generate multiple paths and dump them all to add_path instead of >> returning a FdwPlan struct.
> Multiple valuable Paths for a scan of a foreign table by FDW, but > changing PlanForeignScan to return list of FdwPlan in 9.2 seems too > hasty. I would really like to see that happen in 9.2, because the longer we let that mistake live, the harder it will be to change. More and more FDWs are getting written. I don't think it's that hard to do: we just have to agree that PlanForeignScan should return void and call add_path for itself, possibly more than once. If we do that, I'm inclined to think we cou;d get rid of the separate Node type FdwPlan, and just incorporate "List *fdw_private" into ForeignPath and ForeignScan. This does mean that FDWs will be a bit more tightly coupled to the planner, because they'll have to change whenever we add new fields to struct Path; but that is not really something that happens often. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers