This is a discussion on pgsql: Fix choose_bitmap_and() so that partial index predicates are within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- Fix choose_bitmap_and() so that partial index predicates are considered when deciding whether a potential additional indexscan ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Log Message: ----------- Fix choose_bitmap_and() so that partial index predicates are considered when deciding whether a potential additional indexscan is redundant or not. As now coded, any use of a partial index that was already used in a previous AND arm will be rejected as redundant. This might be overly restrictive, but not considering the point at all is definitely bad, as per example in bug #2441 from Arjen van der Meijden. In particular, a clauseless scan of a partial index was *never* considered redundant by the previous coding, and that's surely wrong. Being more flexible would also require some consideration of how not to double-count the index predicate's selectivity. Modified Files: -------------- pgsql/src/backend/optimizer/path: indxpath.c (r1.205 -> r1.206) (http://developer.postgresql.org/cvsw...1.205&r2=1.206) ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|