pt-query-digest dosn't fingerprint true/false literals correctly
Bug #965553 reported by
Rob Smith
on 2012-03-26
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Percona Toolkit moved to https://jira.percona.com/projects/PT |
Fix Released
|
Medium
|
Frank Cizmich |
Bug Description
Query:
INSERT INTO tbl VALUES ( 123 , false, true, 456);
Distills to
INSERT INTO tbl VALUES ( ? , false, true, ?);
I believe the true/false literals should distill into ?s
This is with pt-query-digest 2.0.4
Related branches
lp:~percona-toolkit-dev/percona-toolkit/pt-query-digest-does-not-fingerprint-true-false-literals-correctly-965553
- Daniel Nichter: Approve on 2014-05-28
-
Diff: 364 lines (+89/-17)7 files modifiedbin/pt-index-usage (+18/-4)
bin/pt-kill (+18/-4)
bin/pt-query-digest (+3/-1)
bin/pt-table-usage (+18/-4)
bin/pt-upgrade (+18/-4)
lib/QueryRewriter.pm (+2/-0)
t/lib/QueryRewriter.t (+12/-0)
Baron Schwartz (baron-xaprb) wrote : | #1 |
Changed in percona-toolkit: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Daniel Nichter (daniel-nichter)
on 2013-08-02
Changed in percona-toolkit: | |
milestone: | none → 2.2.5 |
Daniel Nichter (daniel-nichter)
on 2013-08-03
summary: |
- pt-query-digest fails to distill true/false literals correctly + pt-query-digest dosn't fingerprint true/false literals correctly |
Daniel Nichter (daniel-nichter)
on 2013-09-17
Changed in percona-toolkit: | |
milestone: | 2.2.5 → none |
Frank Cizmich (frank-cizmich)
on 2014-05-27
Changed in percona-toolkit: | |
assignee: | nobody → Frank Cizmich (frank-cizmich) |
milestone: | none → 2.2.8 |
status: | Confirmed → In Progress |
Daniel Nichter (daniel-nichter)
on 2014-05-28
tags: | added: fingerprints |
Changed in percona-toolkit: | |
status: | In Progress → Fix Committed |
Hrvoje Matijakovic (hrvojem)
on 2014-06-04
Changed in percona-toolkit: | |
status: | Fix Committed → Fix Released |
Shahriyar Rzayev (rzayev-sehriyar) wrote : | #2 |
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/
To post a comment you must log in.
Agree -- that should be handled. I'm not sure how many cases like this there will be.