pt-query-digest fails to parse timestamp with no query

[Ovais Tariq]

Brian I am reporting this as a bug in relation to what we talked about the problem I was facing with getting pt-query-digest to parse the slow log.

# pt-query-digest --version
pt-query-digest 2.1.5

The tool pt-query-digest fails to parse the slow log for queries if the queries are prefixed by SET timestamp=xxx. Removing the "SET timestamp=xxx" statements from the slow log fixes the issue and pt-query-digest then works as expected.

[Ovais Tariq (ovais-tariq)]

I would like to add that this bug affects those who use this feature of Percona Server: http://www.percona.com/doc/percona-server/5.5/diagnostics/slow_extended_55.html#slow_query_log_timestamp_always

[Brian Fraser (fraserbn)]

Related bug: https://bugs.launchpad.net/percona-toolkit/+bug/1082599

[Daniel Nichter (daniel-nichter)]

This should work already: SlowLogParser.pm knows about SET statements. Maybe the format of those statements has changed. If you could provide a sample log that causes the problem, Ovais, that would be great. Else I'll try to reproduce it.

[Ovais Tariq (ovais-tariq)]

Daniel,

I have attached the log file that pt-query-digest is failing to parse. Note that removing "set timestamp = xxx" from the log fixes the issue.

For example use the attached slow.log file as follows and pt-query-digest will not parse it correctly:
cat slow.log | pt-query-digest

However, remove the SET TIMESTAMP = xx line and everything works fine:
cat slow.log | sed '/SET timestamp/d' | pt-query-digest

[Shahriyar Rzayev (rzayev-sehriyar)]

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