mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 03:52:35 +01:00
45b6edb158
This bug manifests due to wrong computation and evaluation of keyinfo->key_length. The issues were: * Using table->file->max_key_length() as an absolute value that must not be reached for a key, while it represents the maximum number of bytes possible for a table key. * Incorrectly computing the keyinfo->key_length size during KEY_PART_INFO creation. The metadata information regarding the key such the field length (for strings) was added twice.
18 lines
739 B
Text
18 lines
739 B
Text
# Test case for MDEV-6838.
|
|
# Due to incorrect key_length computation, this usecase failed with the error
|
|
# Using too big key for internal temp table.
|
|
|
|
CREATE TABLE t1 (i INT, state VARCHAR(997)) ENGINE=MyISAM;
|
|
INSERT INTO t1 VALUES (2,'Louisiana'),(9,'Maine');
|
|
|
|
CREATE TABLE t2 (state VARCHAR(997), j INT) ENGINE=MyISAM;
|
|
INSERT INTO t2 VALUES ('Louisiana',9),('Alaska',5);
|
|
INSERT INTO t2 SELECT t2.* FROM t2 JOIN t2 AS t3 JOIN t2 AS t4 JOIN t2 AS t5 JOIN t2 AS t6;
|
|
|
|
SET @@max_heap_table_size= 16384;
|
|
set @@optimizer_switch='derived_merge=OFF';
|
|
set @@optimizer_switch='extended_keys=ON';
|
|
|
|
SELECT * FROM t1 AS t1_1 LEFT JOIN ( t1 AS t1_2 INNER JOIN (SELECT * FROM t2) v2 ON t1_2.i = j ) ON t1_1.state = v2.state LIMIT 1;
|
|
|
|
DROP TABLE t1, t2;
|