mysqldumpslow in 5.1.42 fails to parse slow log correctly

Bug #617099 reported by Peiran Song
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona patches
New
Undecided
Unassigned

Bug Description

Server version: 5.1.45-log Percona SQL Server (GPL), XtraDB 10.2, Revision 89

When run
  $mysqldumpslow <logfile>

Results are like:

Count: 1 Time=0.00s (0s) Lock=0.00s (0s) Rows=0.0 (0), dbm[dbm]@[10.10.101.211]
  # Thread_id: N Schema: pandora Last_errno: N Killed: N
  # Query_time: N.N Lock_time: N.N Rows_sent: N Rows_examined: N Rows_affected: N Rows_read: N
  # Bytes_sent: N Tmp_tables: N Tmp_disk_tables: N Tmp_table_sizes: N
  # InnoDB_trx_id: N
  # InnoDB_IO_r_ops: N InnoDB_IO_r_bytes: N InnoDB_IO_r_wait: N.N
  # InnoDB_rec_lock_wait: N.N InnoDB_queue_wait: N.N
  # InnoDB_pages_distinct: N
  SET timestamp=N;
  truncate table message_body2_20100802

A couple problems:
1) the stats line shows 0 for Time, Lock time, and Rows
2) numbers in header section were mistakenly abstracted out

Thanks for looking into it!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.