percona-discussion team mailing list archive

[Morgan Tocker <tocker@xxxxxxxxx>]

Public bug reported:

The slow query log seems to have an annoying optimization that it will
omit the 'Time' information if subsequent queries are in the same
second, i.e.

# Time: 090402  9:23:36 # User@Host: XXX @ XXX [10.X.X.X]
# Thread_id: 1234  Schema: test
# Query_time: 0.075976  Lock_time: 0.000000  Rows_sent: 0  Rows_examined: 0
SELECT * FROM my_table;
# User@Host: XXX @ XXX [10.X.X.X]
# Thread_id: 1235  Schema: test
# Query_time: 0.651959  Lock_time: 0.000000  Rows_sent: 0  Rows_examined: 0
SELECT * FROM another_table;

This makes it very hard to simply grep the file, since it requires some
sort of parser.

** Affects: percona-patches
     Importance: Undecided
         Status: New

-- 
Slow query log does not always show Date/Time
https://bugs.launchpad.net/bugs/357754
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona patches.

Status in Patches for MySQL by Percona: New

Bug description:
The slow query log seems to have an annoying optimization that it will omit the 'Time' information if subsequent queries are in the same second, i.e.

# Time: 090402  9:23:36 # User@Host: XXX @ XXX [10.X.X.X]
# Thread_id: 1234  Schema: test
# Query_time: 0.075976  Lock_time: 0.000000  Rows_sent: 0  Rows_examined: 0
SELECT * FROM my_table;
# User@Host: XXX @ XXX [10.X.X.X]
# Thread_id: 1235  Schema: test
# Query_time: 0.651959  Lock_time: 0.000000  Rows_sent: 0  Rows_examined: 0
SELECT * FROM another_table;

This makes it very hard to simply grep the file, since it requires some sort of parser.