mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Make GiST index searches smarter about queries against empty ranges.

Browse Source 
In the cases where the result of the called proc is negated, we should
explicitly test both inputs for empty, to ensure we'll never return "true"
for an unsatisfiable query.  In other cases we can rely on the called proc
to say the right thing.
This commit is contained in:
Tom Lane 2011-11-26 14:27:05 -05:00
parent 6c8768c386
commit 5966bcecf6
1 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
src/backend/utils/adt/rangetypes_gist.c
View File

@ -444,13 +444,13 @@ range_gist_consistent_int(FmgrInfo *flinfo, StrategyNumber strategy,
switch (strategy)
{
case RANGESTRAT_BEFORE:
if (RangeIsEmpty(key))
if (RangeIsEmpty(key) || RangeIsEmpty(DatumGetRangeType(query)))
return false;
proc = range_overright;
negate = true;
break;
case RANGESTRAT_OVERLEFT:
if (RangeIsEmpty(key))
if (RangeIsEmpty(key) || RangeIsEmpty(DatumGetRangeType(query)))
return false;
proc = range_after;
negate = true;
@ -459,13 +459,13 @@ range_gist_consistent_int(FmgrInfo *flinfo, StrategyNumber strategy,
proc = range_overlaps;
break;
case RANGESTRAT_OVERRIGHT:
if (RangeIsEmpty(key))
if (RangeIsEmpty(key) || RangeIsEmpty(DatumGetRangeType(query)))
return false;
proc = range_before;
negate = true;
break;
case RANGESTRAT_AFTER:
if (RangeIsEmpty(key))
if (RangeIsEmpty(key) || RangeIsEmpty(DatumGetRangeType(query)))
return false;
proc = range_overleft;
negate = true;
@ -483,6 +483,11 @@ range_gist_consistent_int(FmgrInfo *flinfo, StrategyNumber strategy,
proc = range_contains;
break;
case RANGESTRAT_CONTAINED_BY:
/*
* Ideally we'd apply range_overlaps here, but at present it
* might fail to find empty ranges in the index, which should
* be reported as being contained by anything. This needs work.
*/
return true;
break;
case RANGESTRAT_CONTAINS_ELEM: