delta/mariadb-git.git/sql/opt_range_mrr.cc, branch bb_mdev14101 github.com: MariaDB/server.git MDEV-16934 Query with very large IN clause lists runs slowly 2018-08-17T21:28:39+00:00 Igor Babaev igor@askmonty.org 2018-08-17T21:27:42+00:00 4eac5df3fcebb1adf52e33d9d88dc05bc1e339ce This patch introduces support for the system variable eq_range_index_dive_limit that existed in MySQL starting from 5.6. The variable sets a limit for index dives into equality ranges. Index dives are performed by optimizer to estimate the number of rows in range scans. Index dives usually provide good estimate but they are pretty expensive. To estimate the number of rows in equality ranges statistical data on indexes can be employed. Its usage gives not so good estimates but it's cheap. So if the number of equality dives required by an index scan exceeds the set limit no dives for equality ranges are performed by the optimizer for this index. As the new system variable is introduced in a stable version the default value for it is set to a special value meaning there is no limit for the number of index dives performed by the optimizer. The patch partially uses the MySQL code for WL 5957 'Statistics-based Range optimization for many ranges'. 
This patch introduces support for the system variable eq_range_index_dive_limit
that existed in MySQL starting from 5.6. The variable sets a limit for
index dives into equality ranges. Index dives are performed by optimizer
to estimate the number of rows in range scans. Index dives usually provide
good estimate but they are pretty expensive. To estimate the number of rows
in equality ranges statistical data on indexes can be employed. Its usage gives
not so good estimates but it's cheap. So if the number of equality dives
required by an index scan exceeds the set limit no dives for equality
ranges are performed by the optimizer for this index.

As the new system variable is introduced in a stable version the default
value for it is set to a special value meaning there is no limit for the number
of index dives performed by the optimizer.

The patch partially uses the MySQL code for WL 5957
'Statistics-based Range optimization for many ranges'.
Windows : Fix truncation warnings in sql/ 2017-10-10T06:19:50+00:00 Vladislav Vaintroub wlad@mariadb.com 2017-10-09T19:53:27+00:00 dc93ce8dea9136889f96659bbee15f9f265d6389 






Correct FSF address
2017-03-10T17:21:29+00:00

iangilfillan
github@greenman.co.za

2017-02-10T11:26:55+00:00

f0ec34002a98eeb669cb254eaba6a3d678a58cc1












MDEV-10325: Queries examines all rows of a tables when it should not
2016-07-12T18:49:16+00:00

Sergei Petrunia
psergey@askmonty.org

2016-07-11T19:01:24+00:00

0bb5d955423c2a7b29eab02e7bf6194ae003ae75

The problem was introduced by 1859caf60b725f81f2ac6091eb44cb848a4a439a:
  MDEV-10175: range optimizer calls records_in_range() for full extended keys

  Make the range optimizer not call records_in_range() when it would
  not give any benefit.

that patch used an incorrect way to check for full extended key. Now fixing
the check.





The problem was introduced by 1859caf60b725f81f2ac6091eb44cb848a4a439a:
  MDEV-10175: range optimizer calls records_in_range() for full extended keys

  Make the range optimizer not call records_in_range() when it would
  not give any benefit.

that patch used an incorrect way to check for full extended key. Now fixing
the check.







MDEV-10175: range optimizer calls records_in_range() for full extended keys
2016-06-03T11:43:08+00:00

Sergei Petrunia
psergey@askmonty.org

2016-06-03T11:43:08+00:00

1859caf60b725f81f2ac6091eb44cb848a4a439a

Make the range optimizer not call records_in_range() when it would
not give any benefit.





Make the range optimizer not call records_in_range() when it would
not give any benefit.







10.0-monty merge
2013-07-21T14:39:19+00:00

Sergei Golubchik
sergii@pisem.net

2013-07-21T14:39:19+00:00

b7b5f6f1ab49948b0e15b762266d4640b3d6b7fb

includes:
* remove some remnants of "Bug#14521864: MYSQL 5.1 TO 5.5 BUGS PARTITIONING"
* introduce LOCK_share, now LOCK_ha_data is strictly for engines
* rea_create_table() always creates .par file (even in "frm-only" mode)
* fix a 5.6 bug, temp file leak on dummy ALTER TABLE





includes:
* remove some remnants of "Bug#14521864: MYSQL 5.1 TO 5.5 BUGS PARTITIONING"
* introduce LOCK_share, now LOCK_ha_data is strictly for engines
* rea_create_table() always creates .par file (even in "frm-only" mode)
* fix a 5.6 bug, temp file leak on dummy ALTER TABLE







Push a lot of small fixes to get larger parts to compile
2013-05-21T19:00:08+00:00

Michael Widenius
monty@askmonty.org

2013-05-21T19:00:08+00:00

3143ad589a24ac7581e2195ba0dc13576cb3c9da












Temporary commit of 10.0-merge
2013-03-25T22:03:13+00:00

Michael Widenius
monty@askmonty.org

2013-03-25T22:03:13+00:00

068c61978e3a81836d52b8caf11e044290159ad1












The pilot patch for mwl#253.
2013-03-11T14:44:24+00:00

Igor Babaev
igor@askmonty.org

2013-03-11T14:44:24+00:00

fc1c8ffdadfd14eb51969ecfde43e3204f10f6f8












MDEV-3934 Assertion `((keypart_map+1) & keypart_map) == 0' failed in _mi_pack_key with an index on a POINT column
2013-01-20T13:06:33+00:00

Sergei Golubchik
sergii@pisem.net

2013-01-20T13:06:33+00:00

7caa80c48170f8a35ef8ece7a1881fe1f0e022dd

sel_arg_range_seq_next(): set keypart map also for GEOM_FLAG keys





sel_arg_range_seq_next(): set keypart map also for GEOM_FLAG keys