diff options
author | Sergei Petrunia <psergey@askmonty.org> | 2020-04-29 01:13:52 +0300 |
---|---|---|
committer | Sergei Petrunia <psergey@askmonty.org> | 2020-04-29 01:13:52 +0300 |
commit | 05bf5c020a085cccc442066866ee50df862cf85a (patch) | |
tree | e5652ccc755ca35154bbc28a7b4318e8656d7955 /sql/rpl_rli.h | |
parent | 503fd2115bdc79f0b005917e058855411fdeb691 (diff) | |
download | mariadb-git-bb-10.4-mdev22401.tar.gz |
MDEV-22401: Optimizer trace: multi-component range is not printed correctlybb-10.4-mdev22401
KEY_MULTI_RANGE::range_flag does not have correct flag bits for
per-endpoint flags (NEAR_MIN, NEAR_MAX, NO_MIN_RANGE, NO_MAX_RANGE).
It only has bits for flags that describe both endpoints.
So
- Document this.
- Switch optimizer trace to using {start|end}_key.flag values, instead.
This fixes the bug.
- Switch records_in_column_ranges() to doing that too. (This used to
work, because KEY_MULTI_RANGE::range_flag had correct flag value
for the last key component, and EITS only uses one-component
pseudo-indexes)
Diffstat (limited to 'sql/rpl_rli.h')
0 files changed, 0 insertions, 0 deletions