postgresql/src/backend/optimizer/path
Tom Lane fa559a86ee Adjust indexscan planning logic to keep RestrictInfo nodes associated
with index qual clauses in the Path representation.  This saves a little
work during createplan and (probably more importantly) allows reuse of
cached selectivity estimates during indexscan planning.  Also fix latent
bug: wrong plan would have been generated for a 'special operator' used
in a nestloop-inner-indexscan join qual, because the special operator
would not have gotten into the list of quals to recheck.  This bug is
only latent because at present the special-operator code could never
trigger on a join qual, but sooner or later someone will want to do it.
2004-01-05 23:39:54 +00:00
..
allpaths.c Add the ability to extract OR indexscan conditions from OR-of-AND 2004-01-05 05:07:36 +00:00
clausesel.c Dept. of second thoughts: clause_selectivity shouldn't try to cache its 2004-01-05 16:44:40 +00:00
costsize.c Adjust indexscan planning logic to keep RestrictInfo nodes associated 2004-01-05 23:39:54 +00:00
indxpath.c Adjust indexscan planning logic to keep RestrictInfo nodes associated 2004-01-05 23:39:54 +00:00
joinpath.c Add the ability to extract OR indexscan conditions from OR-of-AND 2004-01-05 05:07:36 +00:00
joinrels.c Repair planner failure when there are multiple IN clauses, each with 2003-12-17 17:07:48 +00:00
Makefile $Header: -> $PostgreSQL Changes ... 2003-11-29 19:52:15 +00:00
orindxpath.c Adjust indexscan planning logic to keep RestrictInfo nodes associated 2004-01-05 23:39:54 +00:00
pathkeys.c Planner failed to be smart about binary-compatible expressions in pathkeys 2003-12-03 17:45:10 +00:00
tidpath.c $Header: -> $PostgreSQL Changes ... 2003-11-29 19:52:15 +00:00