delta/mariadb-git.git/sql/opt_range_mrr.cc, branch 10.56-MDEV-30986

Merge 10.3 into 10.4

2020-05-30T08:04:27+00:00

Merge 10.2 into 10.3

2020-05-27T14:10:39+00:00

Merge 10.1 into 10.2

2020-05-26T10:01:34+00:00

MDEV-21495: Conditional jump or move depends on uninitialised value in sel_arg_range_seq_next

2020-05-25T20:27:00+00:00

Initialize the parameter PARAM::max_key_part when we iterate over the ranges to get estimates
from EITS.

MDEV-22401: Optimizer trace: multi-component range is not printed correctly

2020-04-29T13:31:16+00:00

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)

MDEV-20740: Odd computations in calculate_cond_selectivity_for_table

2019-10-04T17:18:31+00:00

Make SEL_ARG graph traversal code in sel_arg_range_seq_next() set
max_key_parts first.

(Pushing to 10.4 first)

MDEV-18741: Optimizer trace: multi-part key ranges are printed incorrectly

2019-05-28T11:47:44+00:00

Changed the function append_range_all_keyparts to use sel_arg_range_seq_init / sel_arg_range_seq_next to produce ranges.
Also adjusted to print format for the ranges, now the ranges are printed as:
    (keypart1_min, keypart2_min,..)  OP (keypart1_name,keypart2_name, ..) OP (keypart1_max,keypart2_max, ..)

Also added more tests for range and index merge access for optimizer trace

Merge 10.2 into 10.3

2019-05-14T14:18:46+00:00

Merge 10.1 into 10.2

2019-05-13T14:54:04+00:00

Merge branch '5.5' into 10.1

2019-05-11T16:15:57+00:00