Use a hopefully-more-reliable method of detecting default selectivity
authorTom Lane <[email protected]>
Tue, 9 Nov 2004 00:34:46 +0000 (00:34 +0000)
committerTom Lane <[email protected]>
Tue, 9 Nov 2004 00:34:46 +0000 (00:34 +0000)
commit547bb4a7f2bdccad9253a99211ce84b3f9de485a
tree0b7c0663dc838f3e7c6400df21959002e03e6beb
parente4387116da7d9358f3d6801fe59585e8b9890f46
Use a hopefully-more-reliable method of detecting default selectivity
estimates when combining the estimates for a range query.  As pointed out
by Miquel van Smoorenburg, the existing check for an impossible combined
result would quite possibly fail to detect one default and one non-default
input.  It seems better to use the default range query estimate in such
cases.  To do so, add a check for an estimate of exactly DEFAULT_INEQ_SEL.
This is a bit ugly because it introduces additional coupling between
clauselist_selectivity and scalarltsel/scalargtsel, but it's not like
there wasn't plenty already...
src/backend/optimizer/path/clausesel.c
src/backend/utils/adt/selfuncs.c
src/include/utils/selfuncs.h