postgresql/src/backend/optimizer/path
Tom Lane 4e89bae704 Revert the logic for expanding AND/OR conditions in pred_test() to what
it was in 7.4, and add some comments explaining why it has to be this way.
I broke it for OR'd index predicates in a fit of code cleanup last summer.
Per example from Sergey Koshcheyev.
2005-03-01 00:24:52 +00:00
..
allpaths.c Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00
clausesel.c Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00
costsize.c Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00
indxpath.c Revert the logic for expanding AND/OR conditions in pred_test() to what 2005-03-01 00:24:52 +00:00
joinpath.c The result of a FULL or RIGHT join can't be assumed to be sorted by the 2005-01-23 02:21:36 +00:00
joinrels.c Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00
Makefile $Header: -> $PostgreSQL Changes ... 2003-11-29 19:52:15 +00:00
orindxpath.c Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00
pathkeys.c The result of a FULL or RIGHT join can't be assumed to be sorted by the 2005-01-23 02:21:36 +00:00
tidpath.c Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00