Hi, I am trying to use the Volcano planner in order to optimise queries based on statistics but I am having some issues understanding how to achieve this, even after looking at the Github repository for tests. A first goal I would like to achieve would be to choose a join implementation based on its cost.
For example, a query tree can have several joins, and depending on the position of the join in the tree, an certain implementation would be more efficient than another. Would that be possible ? If so, could you share a code snippet ? Thanks -- Campinas Stéphane
