AUTO_INCREMENT columns must be skipped by the --innodb-optimize-keys optimization in mysqldump
Bug #812179 reported by
Alexey Kopytov
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Alexey Kopytov | ||
| 5.1 |
Fix Released
|
High
|
Alexey Kopytov | ||
| 5.5 |
Fix Released
|
High
|
Alexey Kopytov | ||
| Rnt-5.1 |
Fix Released
|
High
|
Alexey Kopytov | ||
Bug Description
Since AUTO_INCREMENT columns must be defined as keys, omitting key specifications and then adding them back in ALTER TABLE doesn't work for them.
mysqldump --innodb-
Related branches
lp:~akopytov/percona-server/bug812179-5.1
- Laurynas Biveinis (community): Approve
-
Diff: 250 lines (+153/-8)1 file modifiedpatches/innodb_expand_fast_index_creation.patch (+153/-8)
lp:~akopytov/percona-server/bug812179-5.5
- Laurynas Biveinis (community): Approve
-
Diff: 250 lines (+153/-8)1 file modifiedpatches/innodb_expand_fast_index_creation.patch (+153/-8)
| tags: | added: cr i14678 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/