pt-duplicate-key-checker provide a bad advice

Bug #1732324 reported by gshliu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
New
Undecided
Unassigned

Bug Description

pt-duplicate-key-checker 2.2.2

# Uniqueness of uniq_operator_mercno_oper ignored because uniq_operator is a stronger constraint
# uniq_operator_mercno_oper is a left-prefix of idx_operator_mercno_oper_cretime
# Key definitions:
# UNIQUE KEY `uniq_operator_mercno_oper` (`merc_no`,`operator`),
# KEY `idx_operator_mercno_oper_cretime` (`merc_no`,`operator`,`create_time`),
# Column types:
# `merc_no` varchar(60) not null default '' comment '?????'
# `operator` varchar(40) not null default '' comment '???????'
# `create_time` timestamp not null default '2017-03-31 00:00:00' comment '????'
# To remove this duplicate index, execute:
ALTER TABLE `bf_merchant_portal`.`portal_operator_pay_info` DROP INDEX `uniq_operator_mercno_oper`;

#I think drop index `idx_operator_mercno_oper_cretime` is better ,not the unique key.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1457

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.