pt-query-advisor should detect mixed data types

Bug #968639 reported by Baron Schwartz on 2012-03-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to
Won't Fix

Bug Description

Here is a scenario pt-query-advisor does not catch:

... user_id IN ('11', '12', 13, 14);

This will cause a full table scan. In addition, the following types of queries are extremely unclear -- it is anyone's guess what the precedence of types and operators are:

... user_id between '11' and 12;

... created_timestamp between 1 and '2012-03-29';

Daniel Nichter (daniel-nichter) wrote :

pt-query-advisor was removed in 2.2. Use pt-query-advisor 2.1 or the online tool:

This issue has been moved to

Changed in percona-toolkit:
status: Confirmed → Won't Fix

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers