Bug #73974 | trunk - slow query log shows some bogus SET timestamp=4294966218; value | ||
---|---|---|---|
Submitted: | 18 Sep 2014 21:41 | Modified: | 28 Sep 2015 19:08 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Logging | Severity: | S3 (Non-critical) |
Version: | 5.7.6 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | slow query log, timestamp, WL6661 |
[18 Sep 2014 21:41]
Shane Bester
[20 Sep 2014 21:05]
MySQL Verification Team
The fix is simple: === modified file 'sql/log.cc' --- sql/log.cc 2014-09-04 11:03:17 +0000 +++ sql/log.cc 2014-09-20 20:54:44 +0000 @@ -785,7 +785,7 @@ timestamp to the slow log */ end= my_stpcpy(end, ",timestamp="); - end= int10_to_str((long) current_utime / 1000000, end, 10); + end= int10_to_str((long) (current_utime / 1000000), end, 10); if (end != buff) {
[20 Sep 2014 21:19]
MySQL Verification Team
regression caused by: WL#6661: Error logging: Allow control of verbosity
[28 Sep 2015 19:08]
Paul DuBois
Noted in 5.7.9, 5.8.0 changelogs. Timestamp values written to the slow query log could be incorrect.