49
--echo # Bug#42064: low memory crash when importing hex strings, in Item_hex_string::Item_hex_string
52
CREATE TABLE t1(a BLOB);
54
SET SESSION debug="+d,bug42064_simulate_oom";
55
# May fail with either ER_OUT_OF_RESOURCES or EE_OUTOFMEMORY
56
--error ER_OUT_OF_RESOURCES, 5
57
INSERT INTO t1 VALUES("");
58
SET SESSION debug=DEFAULT;
63
-- echo # Bug#41660: Sort-index_merge for non-first join table may require
64
-- echo # O(#scans) memory
67
CREATE TABLE t1 (a INT);
68
INSERT INTO t1 VALUES (0), (1), (2), (3), (4), (5), (6), (7), (8), (9);
70
CREATE TABLE t2 (a INT, b INT, filler CHAR(100), KEY(a), KEY(b));
71
INSERT INTO t2 SELECT 1000, 1000, 'filler' FROM t1 A, t1 B, t1 C;
72
INSERT INTO t2 VALUES (1, 1, 'data');
74
--echo # the example query uses LEFT JOIN only for the sake of being able to
75
--echo # demonstrate the issue with a very small dataset. (left outer join
76
--echo # disables the use of join buffering, so we get the second table
77
--echo # re-scanned for every record in the outer table. if we used inner join,
78
--echo # we would need to have thousands of records and/or more columns in both
79
--echo # tables so that the join buffer is filled and re-scans are triggered).
81
SET SESSION debug = '+d,only_one_Unique_may_be_created';
83
--replace_column 1 x 2 x 3 x 4 x 5 x 6 x 7 x 8 x 9 x
85
SELECT * FROM t1 LEFT JOIN t2 ON ( t2.a < 10 OR t2.b < 10 );
86
SELECT * FROM t1 LEFT JOIN t2 ON ( t2.a < 10 OR t2.b < 10 );
88
SET SESSION debug = DEFAULT;
50
93
--echo # End of 5.1 tests