Whilst looking and testing pt-upgrade we seem to have found a couple of queries it “can’t parse”. Should it be able to parse all queries from a slow.log on MySQL?
e.g. In the generated report - we can see it’s taken queries from the slow.log - and all bar a couple - they’ve been turned into templates, i.e.
insert into some_table ( field, field, field ) values ( ?, ?, ? )
But for a couple of the queries the ‘template’ version seems to include junk text from the actual query - I’ll try to give an example:
insert into some_table ( field, field, field ) values ( ?, ?groupmetric?local\n???sizemetric???’
As a result it thinks all these query classes are different. The original query includes text such as C:\Filepath\somewhere-dot-com (where dot-com really is dot and com - replaced here to stop the editor from creating it as a link).
It also has a text field that ends in blah\’ (so ‘blah’ + slash, slash single quote)
I’m just wondering if any of these things is likely to give it parsing the queries into classes?