MariaDB

maria:bb-10.3-MDEV-21601

  1. Git
  2. lp:maria
  3. bb-10.3-MDEV-21601
Last commit made on 2020-02-07
Get this branch:
git clone -b bb-10.3-MDEV-21601 https://git.launchpad.net/maria

Branch merges

Branch information

Name:
bb-10.3-MDEV-21601
Repository:
lp:maria

Recent commits

139ed46... by Jan Lindström

MDEV-21667 : Galera test failure on MW-336

Problem seems to be the fact that we did not enforce correct
applier thread numbers after every command that effects them.
Test changes only.

fed6953... by Jan Lindström

MDEV-21601 : Cleanup Galera disabled tests

* Remove those tests that will not be supported on that release.
* Make sure that correct tests are disabled and have MDEVs
* Sort test names

This should not be merged upwards.

dbbe996... by Oleksandr "Sanja" Byelkin

Merge branch 'bb-10.3-release' into 10.3

8b8d333... by Daniel Bartholomew <email address hidden>

bump the VERSION

0152704... by Elena Stepanova

List of unstable tests for 10.3.22 release

e10e922... by Oleksandr "Sanja" Byelkin

Merge branch 'MDEV-21383' into 10.3

7e8a580... by Sergey Petrunia

MDEV-21383: Possible range plan is not used under certain conditions

[Variant 2 of the fix: collect the attached conditions]

Problem:
make_join_select() has a section of code which starts with
 "We plan to scan all rows. Check again if we should use an index."

the code in that section will [unnecessarily] re-run the range
optimizer using this condition:

  condition_attached_to_current_table AND current_table's_ON_expr

Note that the original invocation of range optimizer in
make_join_statistics was done using the whole select's WHERE condition.
Taking the whole select's WHERE condition and using multiple-equalities
allowed the range optimizer to infer more range restrictions.

The fix:
- Do range optimization using a condition that is an AND of this table's
condition and all of the previous tables' conditions.
- Also, fix the range optimizer to prefer SEL_ARGs with type=KEY_RANGE
over SEL_ARGS with type=MAYBE_KEY, regardless of the key part.
Computing
key_and(
  SEL_ARG(type=MAYBE_KEY key_part=1),
  SEL_ARG(type=KEY_RANGE, key_part=2)
)
will now produce the SEL_ARG with type=KEY_RANGE.

ceda5f7... by Oleksandr "Sanja" Byelkin

Merge branch '10.2' into 10.3

f2ccfca... by Oleksandr "Sanja" Byelkin

Merge branch '10.1' into 10.2

ac3e3e1... by Marko Mäkelä

MDEV-21509: Work around occasional lost DEBUG_SYNC