summaryrefslogtreecommitdiff
path: root/win
diff options
context:
space:
mode:
authorIgor Babaev <igor@askmonty.org>2020-03-14 19:58:57 -0700
committerIgor Babaev <igor@askmonty.org>2020-03-14 19:58:57 -0700
commit407b0a6ae7c300f34535be59dcdb8ba8f84d1ce5 (patch)
treeea93eced5acd25a8aaf038afa8f07dbd0ec8ad72 /win
parent5af12e463549e4bbc2ce6ab720d78937d5e5db4e (diff)
downloadmariadb-git-407b0a6ae7c300f34535be59dcdb8ba8f84d1ce5.tar.gz
MDEV-10466 Server crashed in SEL_ARG::store_min() with extended_keys=on
This bug could manifest itself in a very rare cases when the optimizer chose an execution plan by which a joined table was accessed by a table scan and the optimizer was checking whether ranges checked for each record could improve this plan. In such cases the optimizer evaluates range conditions over a table that depend on other tables. For such conditions the constructed SEL_ARG trees are marked as MAYBE_KEY. If a SEL_ARG object constructed for a sargable condition marked as RANGE_KEY had the same first key part as a MAYBE_KEY SEL_ARG object and the key_and() function was called for this pair of SEL_ARG objects then an invalid SEL_ARG object could be constructed that ultimately could lead to a crash before the execution phase.
Diffstat (limited to 'win')
0 files changed, 0 insertions, 0 deletions