Expanded fast index creation inadvertently uses the fast index creation for temp tables
Bug #999641 reported by
Laurynas Biveinis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Invalid
|
High
|
Unassigned | ||
5.5 |
Invalid
|
High
|
Unassigned |
Bug Description
MySQL has disabled fast index creation for InnoDB temp tables: http://
The Percona Server expanded fast index creation inadvertently uses it for some indexes on temporary tables (bug 999147): : when there is an already-existing secondary index on the table, it will be dropped from the new temp table and recreated after copying the data.
This is not a particularly well-tested code path (bug 999147 is one example what may go wrong). Either let's fully disable it, either test and fully enable it, in process fixing the upstream 39833.
tags: | added: expand-fast-index-creation |
To post a comment you must log in.
SET SESSION expand_ fast_index_ creation= ON;
CREATE TEMPORARY TABLE t1 (a INT, b INT, INDEX(a));
ALTER TABLE t1 ADD INDEX (b);