aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/selfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-10-16 15:39:24 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-10-16 15:39:24 -0400
commit9e8da0f75731aaa7605cf4656c21ea09e84d2eb1 (patch)
tree1776d3f5e68d5ab997851fcfcc3cc684a64e2058 /src/backend/utils/adt/selfuncs.c
parent0898d71f66ed884af726556ac9ffc8081dddc757 (diff)
downloadpostgresql-9e8da0f75731aaa7605cf4656c21ea09e84d2eb1.tar.gz
postgresql-9e8da0f75731aaa7605cf4656c21ea09e84d2eb1.zip
Teach btree to handle ScalarArrayOpExpr quals natively.
This allows "indexedcol op ANY(ARRAY[...])" conditions to be used in plain indexscans, and particularly in index-only scans.
Diffstat (limited to 'src/backend/utils/adt/selfuncs.c')
-rw-r--r--src/backend/utils/adt/selfuncs.c7
1 files changed, 0 insertions, 7 deletions
diff --git a/src/backend/utils/adt/selfuncs.c b/src/backend/utils/adt/selfuncs.c
index 8ceea820bdc..96946281dab 100644
--- a/src/backend/utils/adt/selfuncs.c
+++ b/src/backend/utils/adt/selfuncs.c
@@ -6385,14 +6385,7 @@ btcostestimate(PG_FUNCTION_ARGS)
* is that multiple columns dilute the importance of the first column's
* ordering, but don't negate it entirely. Before 8.0 we divided the
* correlation by the number of columns, but that seems too strong.)
- *
- * We can skip all this if we found a ScalarArrayOpExpr, because then the
- * call must be for a bitmap index scan, and the caller isn't going to
- * care what the index correlation is.
*/
- if (found_saop)
- PG_RETURN_VOID();
-
MemSet(&vardata, 0, sizeof(vardata));
if (index->indexkeys[0] != 0)