Bug #85326 mysqldumpslow cannot parse execution times
Submitted: 6 Mar 2017 16:58 Modified: 10 Mar 2017 10:16
Reporter: István Tóth Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.7.17 OS:CentOS (7)
Assigned to: CPU Architecture:Any
Tags: mysqldumpslow

[6 Mar 2017 16:58] István Tóth
Mysqldumpslow cannot parse the times from the mysqlslowlog.

I get the following output for every query, even longer (fragment):

Count: 1  Time=0.00s (0s)  Lock=0.00s (0s)  Rows=0.0 (0), 0users@0hosts
  Time: N-N-06T13:N:N.496602Z
  # User@Host: stoty[stoty] @ hq6-N.netfone.hu [N.N.N.N]  Id: N
  # Query_time: N.N  Lock_time: N.N Rows_sent: N  Rows_examined: N
  SET timestamp=N;
  select t.id a<query removed>

even for queries that always run longer than 0.00 seconds.

How to repeat:
Create a slow query log by a 5.7.17 community server

run the mysqldumplsow command from the distribution on it.

Suggested fix:
I could get it to parse and print the execution times by massaging the regexes around line 100, but then I run into bug #79828, and gave up.

As a workaround, pt-query-digest from the percona toolkit processed the slow log without a problem.
[10 Mar 2017 10:16] MySQL Verification Team
Hello István Tóth,

Thank you for the report.
Lets call this as duplicate of Bug #79828 for now.