diff options
| author | Igor Babaev <igor@askmonty.org> | 2020-09-24 22:02:00 -0700 |
|---|---|---|
| committer | Igor Babaev <igor@askmonty.org> | 2020-09-24 22:02:00 -0700 |
| commit | 3080b7ebe3cf17107f5b21ac135b0e01fef04fe9 (patch) | |
| tree | eb39e65bc24f0e9cedba966718dc095f7b4aeccf /mysql-test/suite | |
| parent | 7c5519c12d46ead947d341cbdcbb6fbbe4d4fe1b (diff) | |
| download | mariadb-git-bb-10.2-mdev-23811.tar.gz | |
MDEV-23811: With large number of indexes optimizer chooses an inefficient planbb-10.2-mdev-23811
This bug could manifest itself for a query with WHERE condition containing
top level OR formula such that each conjunct contained a single-range
condition supported by the same index. One of these range conditions must
be fully covered by another range condition that is used later in the OR
formula. Additionally at least one of these condition should be ANDed with
a sargable range condition supported by a different index.
There were several attempts to fix related problems for OR conditions after
the backport of range optimizer code from MySQL (commit
0e19f3e36f7842583feb6bead2c2600cd620bced). Unfortunately the first of these
fixes contained typo remained unnoticed until recently. This typo bug led
to rejection of valid range accesses. This patch fixed this typo bug.
The fix revealed another two bugs: one in a constructor for SEL_ARG,
the other in the function tree_or(). Both are fixed in this patch.
Diffstat (limited to 'mysql-test/suite')
0 files changed, 0 insertions, 0 deletions