diff options
| author | Varun Gupta <varun.gupta@mariadb.com> | 2020-04-08 17:39:27 +0530 |
|---|---|---|
| committer | Varun Gupta <varun.gupta@mariadb.com> | 2020-04-08 23:47:03 +0530 |
| commit | c1394ab6b5c0830ec09f6afdae11fa82bae1a123 (patch) | |
| tree | de124b4ad7d7a523785fdb4db6fef8ce3fdd5743 /mysql-test/t/range.test | |
| parent | 64b70b09e6ac253b7915f6120ade5e69fa750b18 (diff) | |
| download | mariadb-git-bb-5.5-varun.tar.gz | |
MDEV-22191: Range access is not picked when index_merge_sort_union is turned offbb-5.5-varun
When index_merge_sort_union is turned off only ror scans were considered for range
scans, which is wrong.
To fix the problem ensure both ror scans and non ror scans are considered for range
access
Diffstat (limited to 'mysql-test/t/range.test')
| -rw-r--r-- | mysql-test/t/range.test | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/mysql-test/t/range.test b/mysql-test/t/range.test index 393ca68e945..e93eff1b1af 100644 --- a/mysql-test/t/range.test +++ b/mysql-test/t/range.test @@ -1718,3 +1718,17 @@ where (key1varchar='value1' AND (key2int <=1 OR key2int > 1)); --echo # The following must show col1=12345 for all rows: select * from t1; drop table t1; + +--echo # +--echo # MDEV-22191: Range access is not picked when index_merge_sort_union is turned off +--echo # + +set @save_optimizer_switch=@@optimizer_switch; +set @save_optimizer_switch="index_merge_sort_union=OFF"; +CREATE TABLE t1 (a INT, INDEX(a)); +INSERT INTO t1 VALUES (0),(1),(2),(3),(4),(5),(6),(7),(8),(9); +explain +SELECT * FROM t1 WHERE a > 5; +SELECT * FROM t1 WHERE a > 5; +set @@optimizer_switch=@save_optimizer_switch; +drop table t1; |