postgresql/src/backend/optimizer/path
Tom Lane 547bb4a7f2 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...
2004-11-09 00:34:46 +00:00
..
Makefile $Header: -> $PostgreSQL Changes ... 2003-11-29 19:52:15 +00:00
allpaths.c Clean up handling of inherited-table update queries, per bug report 2004-10-02 22:39:49 +00:00
clausesel.c Use a hopefully-more-reliable method of detecting default selectivity 2004-11-09 00:34:46 +00:00
costsize.c Avoid overflow in cost_sort when work_mem exceeds 1Gb. 2004-10-23 00:05:27 +00:00
indxpath.c pred_test() logic was being too narrow-minded about where it might find 2004-11-05 20:45:10 +00:00
joinpath.c Pgindent run for 8.0. 2004-08-29 05:07:03 +00:00
joinrels.c Pgindent run for 8.0. 2004-08-29 05:07:03 +00:00
orindxpath.c Fix OR-index-scan planner to recognize that a partial index is usable 2004-10-11 22:57:00 +00:00
pathkeys.c Pgindent run for 8.0. 2004-08-29 05:07:03 +00:00
tidpath.c Update copyright to 2004. 2004-08-29 04:13:13 +00:00