PostgreSQL: Backend Flowchart
postgresql.org
postgresql.org
Genetic query optimizer optimizer/path evaluates all possible ways to join the requested tables. When the number of tables becomes great, the number of tests made becomes great too. The Genetic Query Optimizer considers each table separately, then figures the most optimal order to perform the join. For a few tables, this method takes longer, but for a large number of tables, it is faster. There is an option to control when this feature is used.
As it is, given the comment on how to hand-calculate new <area> coordinates embedded near the <map> on the page, I think they just used Graphvis to output a .gif rendering of the flowchart, and then went in and hand-wrote a separate HTML <map> on top of it. Quite a bit more work, and work that would have to be duplicated if you ever wanted to tweak and re-export the graph itself.