From 14c7fba3f7d0769d8a063dea2854693f35535f6a Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 21 Apr 2005 19:18:13 +0000 Subject: 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. --- src/backend/utils/misc/postgresql.conf.sample | 1 + 1 file changed, 1 insertion(+) (limited to 'src/backend/utils/misc/postgresql.conf.sample') diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample index 6b06afcb7fd..b175236883a 100644 --- a/src/backend/utils/misc/postgresql.conf.sample +++ b/src/backend/utils/misc/postgresql.conf.sample @@ -137,6 +137,7 @@ # - Planner Method Configuration - +#enable_bitmapscan = true #enable_hashagg = true #enable_hashjoin = true #enable_indexscan = true -- cgit v1.2.3