Make use of InnoDB fast index creation in mysqldump, ALTER TABLE and OPTIMIZE TABLE
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Undecided
|
Alexey Kopytov | ||
| 5.1 |
Fix Released
|
Undecided
|
Alexey Kopytov | ||
| 5.5 |
Fix Released
|
Undecided
|
Alexey Kopytov | ||
Bug Description
Currently, InnoDB fast index creation can only be used when explicitly creating or dropping indexes.
We can make use of that optimization in mysqldump and ALTER TABLE / OPTIMIZE TABLE. Namely:
1. mysqldump should be updated to dump InnoDB tables so that secondary indexes are created after loading the data.
2. When ALTER TABLE requires a table copy, it can optimize copying the data by temporarily dropping secondary keys before copying and recreating them after it.
3. Since OPTIMIZE TABLE is performed as ALTER TABLE internally, it will benefit from the same optimization as well.
References:
http://
http://
http://
Related branches
- Fred Linhoss (community): Approve (documentation)
- Percona developers: Pending requested
-
Diff: 734 lines (+722/-0)2 files modifiedinnodb_expand_fast_index_creation.patch (+720/-0)
series (+2/-0)
- Fred Linhoss (community): Approve (documentation)
- Vadim Tkachenko: Approve
-
Diff: 731 lines (+719/-0)2 files modifiedinnodb_expand_fast_index_creation.patch (+717/-0)
series (+2/-0)
| tags: | added: fr |
| Alexey Kopytov (akopytov) wrote | #1 |
| Alexey Kopytov (akopytov) wrote | #2 |
| Alexey Kopytov (akopytov) wrote | #3 |
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #4 |
Released in 5.1.56-12.7 and 5.5.11-20.2.