pt-query-digest doesn't display time range on PS 5.7

Bug #1594629 reported by monty solomon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Fix Released
Undecided
Unassigned

Bug Description

On PS 5.6.25 the output of pt-query-digest slow.log (version 2.2.17) looks like this and includes the Time range

# 4.5s user time, 40ms system time, 41.48M rss, 223.34M vsz
# Current date: Tue Jun 21 00:41:31 2016
# Hostname: mute-base
# Files: /opt/mysql/dblogs1/svcmarketplace-p0/gen/slow.log
# Overall: 12.77k total, 226 unique, 0.00 QPS, 0.00x concurrency _________
# Time range: 2016-04-14 14:07:54 to 2016-06-21 00:39:08
# Attribute total min max avg 95% stddev median
# ============ ======= ======= ======= ======= ======= ======= =======

On PS 5.7.12 the output looks like this and does not include the Time range

# 16.2s user time, 50ms system time, 31.16M rss, 208.04M vsz
# Current date: Tue Jun 21 01:03:05 2016
# Hostname: cold-lake
# Files: /opt/mysql/dblogs1/svcmarketplace-p0/gen/slow.log
# Overall: 6.12k total, 18 unique, 0 QPS, 0x concurrency _________________
# Attribute total min max avg 95% stddev median
# ============ ======= ======= ======= ======= ======= ======= =======

Revision history for this message
monty solomon (monty+launchpad) wrote :

Status please.

Revision history for this message
monty solomon (monty+launchpad) wrote :

Does the fix for bug 1581752 fix this bug?

Revision history for this message
monty solomon (monty+launchpad) wrote :

This is fixed in version 2.2.19.

# Query 1: 0.15 QPS, 0.02x concurrency, ID 0x0B061FF1DD0D97EF at byte 116815490
# This item is included in the report because it matches --limit.
# Scores: V/M = 0.04
# Time range: 2016-08-16T01:48:51 to 2016-09-01T00:58:06

Revision history for this message
Carlos Salguero (carlos-salguero) wrote :
Changed in percona-toolkit:
status: New → Triaged
status: Triaged → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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.