Slow query log does not always show Date/Time
Bug #357754 reported by
Morgan Tocker
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona patches |
Fix Released
|
High
|
Unassigned | ||
Percona-XtraDB |
Invalid
|
High
|
Unassigned |
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.
Changed in percona-patches: | |
importance: | Undecided → Medium |
Changed in percona-patches: | |
importance: | Medium → High |
Changed in percona-xtradb: | |
importance: | Undecided → High |
Changed in percona-xtradb: | |
status: | New → Won't Fix |
Changed in percona-patches: | |
status: | New → Confirmed |
Changed in percona-patches: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The new global bool variable timestamp_ every (default: false)
log_slow_
was added.