Bug #67892 Warning recommends to use a deprecated or non-existing option

• Submitted: 13 Dec 2012 2:37
• Modified: 14 Dec 2012 13:18
• Reporter: Elena Stepanova
• Status: Closed
• Category: MySQL Server: Errors
• Severity: S3 (Non-critical)
• Version: 5.5.28, 5.6.9
• OS: Any
• CPU Architecture: Any

[13 Dec 2012 2:37] Elena Stepanova

Description:
(Filing on behalf of our user who reported it on IRC)

If server is started with e.g. --log-slow-admin-statements option, it throws a warning on startup: 
[Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set

It happens even with 5.6, although the option log_slow_queries was deprecated in 5.1 and removed in 5.6, so the server won't start with it.

How to repeat:
- start server with --log-slow-admin-statements but without --slow-query-log;
- check the error log.

Suggested fix:
Change the text of the warning so that it uses the new variable slow-query-log.

[13 Dec 2012 8:45] Valeriy Kravchuk

From recently build 5.6.9-rc:

2012-12-13 10:43:41 0 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set

:)

[13 Dec 2012 11:30] MySQL Verification Team

Thank you for the bug report.

[14 Dec 2012 10:46] Jon Olav Hauglid

Hi Elena. Thanks for the bug report!

Here's a tip in return: Take a look at the warning message printed
when --general-log-file or --slow-query-log-file are used together
with --log-output=table (and not =file).

[14 Dec 2012 13:18] Paul DuBois

Noted in 5.6.10, 5.7.1 changelogs.

Some messages written by the server to the error log referred to the
deprecated --log-slow-queries option rather than the --slow-query-log
option. Similarly, the server referred to the deprecated --log option
rather than the --general-log-file and --log-output options.