pgsql: Fix GEQO to not assume its join order heuristic always works.
От | Tom Lane |
---|---|
Тема | pgsql: Fix GEQO to not assume its join order heuristic always works. |
Дата | |
Msg-id | E1YLMFW-0006KC-Ev@gemulon.postgresql.org обсуждение исходный текст |
Список | pgsql-committers |
Fix GEQO to not assume its join order heuristic always works. Back in commit 400e2c934457bef4bc3cc9a3e49b6289bd761bc0 I rewrote GEQO's gimme_tree function to improve its heuristic for modifying the given tour into a legal join order. In what can only be called a fit of hubris, I supposed that this new heuristic would *always* find a legal join order, and ripped out the old logic that allowed gimme_tree to sometimes fail. The folly of this is exposed by bug #12760, in which the "greedy" clumping behavior of merge_clump() can lead it into a dead end which could only be recovered from by un-clumping. We have no code for that and wouldn't know exactly what to do with it if we did. Rather than try to improve the heuristic rules still further, let's just recognize that it *is* a heuristic and probably must always have failure cases. So, put back the code removed in the previous commit to allow for failure (but comment it a bit better this time). It's possible that this code was actually fully correct at the time and has only been broken by the introduction of LATERAL. But having seen this example I no longer have much faith in that proposition, so back-patch to all supported branches. Branch ------ REL9_2_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/0d083103fc0f14c8ae535d4f7b73c689a22c836d Modified Files -------------- src/backend/optimizer/geqo/geqo_eval.c | 29 +++++++++++++++++++++-------- src/backend/optimizer/geqo/geqo_main.c | 3 +++ src/backend/optimizer/geqo/geqo_pool.c | 26 +++++++++++++++++++++++++- 3 files changed, 49 insertions(+), 9 deletions(-)
В списке pgsql-committers по дате отправления: