Fix GEQO optimizer to work correctly with new outer-join-capable
query representation. Note that GEQO_RELS setting is now interpreted as the number of top-level items in the FROM list, not necessarily the number of relations in the query. This seems appropriate since we are only doing join-path searching over the top-level items.
Showing
- src/backend/optimizer/geqo/geqo_eval.c 29 additions, 21 deletionssrc/backend/optimizer/geqo/geqo_eval.c
- src/backend/optimizer/geqo/geqo_main.c 9 additions, 11 deletionssrc/backend/optimizer/geqo/geqo_main.c
- src/backend/optimizer/geqo/geqo_pool.c 7 additions, 7 deletionssrc/backend/optimizer/geqo/geqo_pool.c
- src/backend/optimizer/path/allpaths.c 2 additions, 2 deletionssrc/backend/optimizer/path/allpaths.c
- src/include/optimizer/geqo.h 7 additions, 5 deletionssrc/include/optimizer/geqo.h
- src/include/optimizer/geqo_pool.h 3 additions, 2 deletionssrc/include/optimizer/geqo_pool.h
Loading
Please register or sign in to comment