Bug #69624 | Sometimes Memory + Events status are printed to error log on mysqld shutdown | ||
---|---|---|---|
Submitted: | 30 Jun 2013 13:48 | Modified: | 26 Nov 2014 15:31 |
Reporter: | Przemyslaw Malkowski | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.5 | OS: | Any |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | COM_DEBUG, debug, error log, mysql_print_status() |
[30 Jun 2013 13:48]
Przemyslaw Malkowski
[30 Jun 2013 14:29]
MySQL Verification Team
Happens on SIGHUP too. Does this answer your question: http://dev.mysql.com/doc/refman/5.6/en/server-signal-response.html
[30 Jun 2013 18:31]
Przemyslaw Malkowski
SIGHUP effect is the same as mysqladmin debug - more debug info is printed into error log (btw the doc about signal responses does not mention the memory nor events status sections). While the debug info that is being logged on server shutdown consists ONLY memory and events status. Also my point is to explain exactly WHEN this information is printed to error log ON SERVER SHUTDOWN (not on SIGHUP).
[24 Jul 2013 10:54]
MySQL Verification Team
Hello Przemyslaw, Thank you for the report. Thanks, Umesh
[26 Nov 2014 15:31]
Paul DuBois
Bug#71346 mentions a feature request that has been filed to better deal with information such as this. Given that feature request, I am closing this docs bug with "Won't fix."