polardbxengine/mysql-test/t/range_with_memory_limit.test

32 lines
913 B
Plaintext

--echo # Bug#17769777 EXCESSIVE MEMORY CONSUMPTION WITH MANY AND / BETWEEN
--echo # ITEMS
--echo # Bug#17413040 USING MANY WHERE CONDITIONS MAKES RANGE SCAN DISABLED
CREATE TABLE t1 (
a INT,
b INT,
KEY (a)
)ENGINE=INNODB;
INSERT INTO t1 VALUES (0, 0), (1, 1), (2, 2), (3, 3), (4, 4), (5, 5), (6, 6),
(7, 7), (8, 8), (9, 9);
ANALYZE TABLE t1;
SET RANGE_OPTIMIZER_MAX_MEM_SIZE= 100;
EXPLAIN SELECT DISTINCT a FROM t1 WHERE (a, b) IN ((0, 0), (1, 1));
SET RANGE_OPTIMIZER_MAX_MEM_SIZE= DEFAULT;
EXPLAIN SELECT DISTINCT a FROM t1 WHERE (a, b) IN ((0, 0), (1, 1));
DROP TABLE t1;
--source include/force_myisam_default.inc
--source include/have_myisam.inc
#Running the entire test suite for range queries to increase the test
#coverage
SET RANGE_OPTIMIZER_MAX_MEM_SIZE= 10;
--source include/range.inc
SET RANGE_OPTIMIZER_MAX_MEM_SIZE= DEFAULT;
--echo # End of test for Bug#17769777 and Bug#17413040