Rethink original decision to use AND/OR Expr nodes to represent bitmap
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 21 Apr 2005 19:18:13 +0000 (19:18 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 21 Apr 2005 19:18:13 +0000 (19:18 +0000)
commit7180f2900451421d3ca3167a4765bb3426ff7033
tree74165f7593ae4aac2514c538f1eadfbd59c8e945
parentf9e007fcd6cac8d3ac7baf4951efe96f625f035f
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.
16 files changed:
doc/src/sgml/runtime.sgml
src/backend/nodes/outfuncs.c
src/backend/optimizer/README
src/backend/optimizer/path/allpaths.c
src/backend/optimizer/path/costsize.c
src/backend/optimizer/plan/createplan.c
src/backend/optimizer/util/pathnode.c
src/backend/tcop/postgres.c
src/backend/utils/misc/guc.c
src/backend/utils/misc/postgresql.conf.sample
src/bin/psql/tab-complete.c
src/include/nodes/nodes.h
src/include/nodes/relation.h
src/include/optimizer/cost.h
src/include/optimizer/pathnode.h
src/test/regress/expected/rangefuncs.out