Bug #56240 please write proper dates to the error log
| Submitted: | 25 Aug 2010 7:13 | Modified: | 10 Dec 2012 16:07 |
|---|---|---|---|
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Logging | Severity: | S4 (Feature request) |
| Version: | 5.1,5.5 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[25 Aug 2010 7:13]
Shane Bester
[25 Aug 2010 7:13]
Shane Bester
it's nearly as irritating as reading time like 1pm instead of 13:00:00 or 13h00
[26 Jul 2012 19:21]
Shane Bester
Appears fixed in Twitter's fork: https://github.com/twitter/mysql/commit/e640361c9a1461d33cb7f09da7586c8addbbab36
[26 Jul 2012 21:03]
Davi Arnaut
Print ISO date and PID with all error log messages. (*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: Print-ISO-date-and-PID-with-all-error-log-messages.patch (application/octet-stream, text), 4.29 KiB.
[10 Dec 2012 16:07]
Paul DuBois
Noted in 5.6.9, 5.7.0 changelogs. mysqld now writes dates to the error log in ISO (YYYY-MM-DD hh:mm:ss) format. It also includes its process ID following the date. Thanks to Davi Arnaut for the patch.
[27 Feb 2013 6:51]
Shane Bester
http://xkcd.com/1179/
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.