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/tcop/postgres.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'src/backend/tcop/postgres.c') diff --git a/src/backend/tcop/postgres.c b/src/backend/tcop/postgres.c index 381d0e61102..2872d939ca8 100644 --- a/src/backend/tcop/postgres.c +++ b/src/backend/tcop/postgres.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/tcop/postgres.c,v 1.442 2005/02/22 04:37:17 momjian Exp $ + * $PostgreSQL: pgsql/src/backend/tcop/postgres.c,v 1.443 2005/04/21 19:18:13 tgl Exp $ * * NOTES * this is the "main" module of the postgres backend and @@ -2371,6 +2371,9 @@ PostgresMain(int argc, char *argv[], const char *username) case 'i': /* indexscan */ tmp = "enable_indexscan"; break; + case 'b': /* bitmapscan */ + tmp = "enable_bitmapscan"; + break; case 't': /* tidscan */ tmp = "enable_tidscan"; break; -- cgit v1.2.3