(2012/02/14 19:42), Shigeru Hanada wrote: > (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. With this change, I think it would also >> have to add a new FDW API that is called from create_foreignscan_plan() >> and lets the FDW generate foreignscan plan for the base relation scanned >> by the best path choosed by postgres optimizer for itself. What do you >> think about it?
> In short, I have some ideas to enhance foreign table scans, but IMO they > are half-baked and we don't have enough time to achieve them for 9.2. OK. Thank you for your answer. Best regards, Etsuro Fujita -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers