Clarity in fast_index_creation Percona documentation
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
| 5.1 |
Won't Fix
|
Medium
|
Borys Belinsky | |||
| 5.5 |
Triaged
|
Medium
|
Borys Belinsky | |||
| 5.6 |
Triaged
|
Medium
|
Borys Belinsky | |||
| 5.7 |
Triaged
|
Medium
|
Borys Belinsky | |||
Bug Description
The page -- http://
1. For expand_
2.
"""
This feature implements a session variable that disables fast index creation. This causes indexes to be created in the way they were created before fast index creation was implemented. While this is slower, it avoids the problem of data dictionary inconsistency between MySQL and InnoDB.
"""
That inconsistency won't be there if both fast_index_creation and
expand_
3. Some or all of the caveats mentioned in http://
4. Add http://
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #1 |
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #2 |
| Changed in percona-server: | |
| status: | New → Confirmed |
| Changed in percona-server: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → Medium |
| Changed in percona-server: | |
| status: | In Progress → Triaged |
| tags: | added: expand-fast-index-creation |
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
Also, provide details on crash resilience on fast_index_creation in general and consequences, any, of it .