xtrabackup export - support tables with more than 31 indexes
Bug #1089681 reported by
Ryan Brothers
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.0 |
Won't Fix
|
Medium
|
Unassigned | |||
2.1 |
Won't Fix
|
Medium
|
Unassigned | |||
2.2 |
Won't Fix
|
Medium
|
Unassigned | |||
2.3 |
Fix Released
|
Medium
|
Vasily Nemkov | |||
2.4 |
Fix Released
|
Medium
|
Vasily Nemkov |
Bug Description
I have a InnoDB table with 50 fields and many of the fields are foreign keys, so because of that, the table has a large number of indexes. I followed the instructions on http://
Looking in xtrabackup.c, there's a error thrown that says "xtrabackup: error: sorry, cannot export over 31 indexes for now."
Can the export in xtrabackup please be modified to support > 31 indexes in a table?
Thanks,
Ryan
To post a comment you must log in.
Yes, the limitation of 31 indexes is implied by the current format of .exp files. Currently, an .exp file is always a 16K page divided into 512-byte segments. The first segment contains the number of indexes and the table name. And the remaining 31 segments contain IDs, root page offsets and names for each index in the table.
This should be easy to fix, as I don't see a reason for an .exp file to take just one page.