Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
5.5(EOL), 10.0(EOL)
-
5.5.48-0
Description
The problem appeared in 5.3 tree with the following revision:
revno: 3793 [merge]
|
revision-id: igor@askmonty.org-20140804170551-76ohozgq308a9f3a
|
parent: sergii@pisem.net-20140801100455-jtqd7ofg3xwau6j1
|
parent: igor@askmonty.org-20140801051743-7i2297y96icyx9vx
|
committer: Igor Babaev <igor@askmonty.org>
|
branch nick: maria-5.3
|
timestamp: Mon 2014-08-04 10:05:51 -0700
|
message:
|
Merge.
|
------------------------------------------------------------
|
revno: 3774.1.1
|
revision-id: igor@askmonty.org-20140801051743-7i2297y96icyx9vx
|
parent: psergey@askmonty.org-20140318080632-c1pql218bfrx26y2
|
committer: Igor Babaev <igor@askmonty.org>
|
branch nick: maria-5.3-mdev5721
|
timestamp: Thu 2014-07-31 22:17:43 -0700
|
message:
|
Fixed bug mdev-5721.
|
Do not define a look-up key for a temporary table if its length
|
exceeds the maximum length of such keys.
|
Test case:
CREATE TABLE t1 (i INT, state VARCHAR(1024)) ENGINE=MyISAM; |
INSERT INTO t1 VALUES (2,'Louisiana'),(9,'Maine'); |
|
|
CREATE TABLE t2 (state VARCHAR(1024), j INT) ENGINE=MyISAM; |
CREATE OR REPLACE ALGORITHM=TEMPTABLE VIEW v2 AS SELECT * FROM t2; |
INSERT INTO t2 VALUES |
('Louisiana',9),('Alaska',5); |
|
|
SELECT * FROM t1 AS t1_1 LEFT JOIN ( t1 AS t1_2 INNER JOIN v2 ON t1_2.i = j ) ON t1_1.state = v2.state; |
|
|
DROP VIEW v2; |
DROP TABLE t1, t2; |
Expected result:
i state i state state j
|
2 Louisiana 9 Maine Louisiana 9
|
9 Maine NULL NULL NULL NULL
|
Actual result:
i state i state state j
|
2 Louisiana NULL NULL NULL NULL
|
9 Maine NULL NULL NULL NULL
|
Attachments
Issue Links
- relates to
-
-
- Closed
-
Activity
it was fixed between 5.5.40 and 5.5.41
git bisect claims that 6f762cdd6c2805d2b912fa858c36dffdb181b755 fixed it (I do not know how that is possible).
The problem disappeared from 5.5 tree after 5.3=>5.5 merge, particularly this change:
commit b75090c7dede338236b98ace65362348579ffa01
|
Author: Sergey Petrunya <psergey@askmonty.org>
|
Date: Thu Dec 18 20:06:49 2014 +0300
|
|
|
MDEV-6830: Server crashes in best_access_path after a sequence of SELECTs ...
|
|
generate_derived_keys_for_table() did not work correctly in the case where
|
- it had a potential index on derived table
|
- however, TABLE::check_tmp_key() would disallow creation of this index
|
after looking at its future key parts (because of the key parts exceeding
|
max. index length)
|
- the code would leave a KEYUSE structure that refers to a non-existant index.
|
Depending on further optimizer calculations, this could cause a crash.
|
Whether it really fixed this bug or just hid it is another question, I don't know that.
sanja, please close this bug if it's really fixed or reassign back to me if there's something to review.
yes