pt-duplicate-key-checker does not re-create indexes with same prefix length
Bug #1214114 reported by
Ryan Lowe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Expired
|
Medium
|
Unassigned |
Bug Description
See summary. Anonymized example:
# #######
# X.Y
# #######
# Key IX_Z ends with a prefix of the clustered index
# Key definitions:
# KEY `IX_Z` (`A`(13),`B`)
# PRIMARY KEY (`B`),
# Column types:
# `B` varchar(767) default null
# `A` decimal(22,0) not null
# To shorten this duplicate clustered index, execute:
ALTER TABLE `X`.`Y` DROP INDEX `IX_Z`, ADD INDEX `IX_A` (`A`);
tags: | added: pt-duplicate-key-checker |
Changed in percona-toolkit: | |
status: | New → Confirmed |
tags: | added: index-prefix |
Changed in percona-toolkit: | |
milestone: | none → 2.2.6 |
importance: | Undecided → Medium |
assignee: | nobody → Daniel Nichter (daniel-nichter) |
Changed in percona-toolkit: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Ryan,
Can you provide a table def that reproduce this? Column A is DECIMAL which doesn't support a prefix as far as I can tell or make MySQL accept. So I don't know how KEY `IX_Z` (`A`(13),`B`) is possible.