-
- Downloads
Rethink original decision to use AND/OR Expr nodes to represent bitmap
logic operations during planning. Seems cleaner to create two new Path node types, instead --- this avoids duplication of cost-estimation code. Also, create an enable_bitmapscan GUC parameter to control use of bitmap plans.
Showing
- doc/src/sgml/runtime.sgml 20 additions, 3 deletionsdoc/src/sgml/runtime.sgml
- src/backend/nodes/outfuncs.c 29 additions, 1 deletionsrc/backend/nodes/outfuncs.c
- src/backend/optimizer/README 1 addition, 0 deletionssrc/backend/optimizer/README
- src/backend/optimizer/path/allpaths.c 7 additions, 1 deletionsrc/backend/optimizer/path/allpaths.c
- src/backend/optimizer/path/costsize.c 113 additions, 75 deletionssrc/backend/optimizer/path/costsize.c
- src/backend/optimizer/plan/createplan.c 44 additions, 86 deletionssrc/backend/optimizer/plan/createplan.c
- src/backend/optimizer/util/pathnode.c 50 additions, 4 deletionssrc/backend/optimizer/util/pathnode.c
- src/backend/tcop/postgres.c 4 additions, 1 deletionsrc/backend/tcop/postgres.c
- src/backend/utils/misc/guc.c 9 additions, 1 deletionsrc/backend/utils/misc/guc.c
- src/backend/utils/misc/postgresql.conf.sample 1 addition, 0 deletionssrc/backend/utils/misc/postgresql.conf.sample
- src/bin/psql/tab-complete.c 2 additions, 1 deletionsrc/bin/psql/tab-complete.c
- src/include/nodes/nodes.h 3 additions, 1 deletionsrc/include/nodes/nodes.h
- src/include/nodes/relation.h 29 additions, 3 deletionssrc/include/nodes/relation.h
- src/include/optimizer/cost.h 6 additions, 3 deletionssrc/include/optimizer/cost.h
- src/include/optimizer/pathnode.h 8 additions, 2 deletionssrc/include/optimizer/pathnode.h
- src/test/regress/expected/rangefuncs.out 12 additions, 11 deletionssrc/test/regress/expected/rangefuncs.out
Loading
Please register or sign in to comment