Issues
- LP #1130994: pt-query-advisor gives false, inconsistent warnings.PT-1077Resolved issue: PT-1077
- LP #1079086: pt-query-advisor shows the same report regardless of --report-formatPT-1047Resolved issue: PT-1047
- LP #1013671: pt-query-advisor --query <DSN option> does not workPT-992Resolved issue: PT-992
- LP #999722: Multi-column IN clause causes false-positive JOI.001PT-971Resolved issue: PT-971
- LP #983191: Wrong advise regarding IP-addressesPT-959Resolved issue: PT-959
- LP #947987: Some tools still use removed package (MySQLDump)PT-945Resolved issue: PT-945
- LP #933469: pt-query-advisor treats distinct() as a functionPT-933Resolved issue: PT-933
- LP #933467: pt-query-advisor doesn't warn on a mixture of aggregates and columns in a non-GROUP-BY queryPT-932Resolved issue: PT-932
- LP #933463: pt-query-advisor doesn't warn about =NULLPT-931Resolved issue: PT-931
- LP #933009: pt-query-advisor doesn't catch UPDATE/SET bugPT-929Resolved issue: PT-929
- LP #932992: pt-query-advisor doesn't warn about FOR UPDATEPT-928Resolved issue: PT-928
- LP #1174956: pt-query-digest and pt-fingerprint don't strip some multi-line commentsPT-798Resolved issue: PT-798
- LP #996069: pt-query-advisor RES.001 is incorrectPT-779Resolved issue: PT-779
- LP #933465: pt-query-advisor false positive on RES.001PT-766Resolved issue: PT-766
- LP #985577: pt-query-advisor doesn't notice JOI.003PT-519Resolved issue: PT-519
- LP #968639: pt-query-advisor should detect mixed data typesPT-506Resolved issue: PT-506
- LP #937234: pt-query-advisor issues wrong RES.001PT-480Resolved issue: PT-480
- LP #937225: pt-query-advisor OUTER JOIN advice in JOI.003 is confusingPT-479Resolved issue: PT-479
- LP #937221: pt-query-advisor gives false JOI.003PT-478Resolved issue: PT-478
- LP #929046: SUB.001, LIT.001 and LIT.002 are sensitive to program statePT-467Resolved issue: PT-467
- LP #823431: pt-query-advisor hangs on big queriesPT-414Resolved issue: PT-414
LP #1130994: pt-query-advisor gives false, inconsistent warnings.
Description
Environment
Smart Checklist
Details
Assignee
UnassignedUnassignedReporter
lpjirasynclpjirasync(Deactivated)Priority
Low
Details
Details
Assignee
Reporter
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Activity
lpjirasyncJanuary 24, 2018 at 7:18 PM
**Comment from Launchpad by: Tramada Systems on: 19-03-2013 23:33:09
Reported behaviour was detected whilst processing large "long queries" logs files and was replicated processing attached sample file.
As reported above, running query-advisor against single queries looks to be giving correct advice.
lpjirasyncJanuary 24, 2018 at 7:18 PM
**Comment from Launchpad by: Daniel Nichter on: 13-03-2013 15:28:51
We have decided to remove pt-query-advisor from 2.2 and refocus our efforts on the online version of the tool: https://tools.percona.com/query-advisor. The attached file is a little difficult to make sense of because the queries are so large and seem to run together. Could you isolate the particular issues and report them at https://github.com/percona/query-advisor/issues please? Also, this means that any fixes for these queries will not be in the command line tool but rather the online tool.
**Reported in Launchpad by Tramada Systems last update 19-03-2013 23:33:10
Command: pt-query-advisor /tmp/sample4pt-query-advisor
Tools version: 2.1.9-1
MySQL version: 5.5.12
Output:
ALI.001 0xD6277F8BD92F2849
RES.002 0xD6277F8BD92F2849
Profile
Query ID NOTE WARN CRIT Item
================== ==== ==== ==== ==========================================
0xD6277F8BD92F2849 1 1 0 select this_.booking_id as booking???, ... from consultant this left outer join consultant consultant?_ on this_.default_buddy_consultant_id=consultant?.consultant_id inner join branch branch? on this_.lvl?branch_id=branch?.branch_id left outer join branch branch?_ on branch?.parent_branch_id=branch?.branch_id inner join role role?_ on this_.role_id=role?_.role_id
RES.002 is incorrectly reported for the last one out of three queries in attached sample file. Actually none of these queries has LIMIT clause, although word "limit" is a part of some column names.
Furthermore, testing with six subset files containing:
single query per file
two queries per file (1+2, 1+3, 2+3)
resulted in:
NO warnings from single query files
RES.002 from 1+2 file
CLA.001 from 1+3 and 2+3 files
CLA.001 warnings are correct as the third query does not have WHERE clause.