On 03.12.2011 01:05, Tom Lane wrote:
Heikki Linnakangas<heikki.linnakan...@enterprisedb.com> writes:
Hmm, so you're saying that the FDW function needs to be able to return
multiple paths for a single joinrel. Fair enough, and that's not
specific to remote joins. Even a single-table foreign scan could be
implemented differently depending on whether you prefer fast-start or
cheapest total.
... or ordered vs unordered, etc. Yeah, good point, we already got this
wrong with the PlanForeignScan API. Good thing we didn't promise that
would be stable.
This discussion withered down here...
I think the advice to Shigeru-san is to work on the API. We didn't reach
a consensus on what exactly it should look like, but at least you need
to be able to return multiple paths for a single joinrel, and should
look at fixing the PlanForeignScan API to allow that too.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
