MySQL Bugs: #111773: The log_queries_not_using

Bug #111773	The log_queries_not_using_indexes for de
Submitted:	17 Jul 2023 9:26	Modified:	17 Jul 2023 13:00
Reporter:	karry zhang (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	ALL	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
The explanation about log_queries_not_using_indexes(https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_log_queries_no...) is as follows:

This option does not necessarily mean that no index is used. For example, a query that uses a full index scan uses an index but would be logged because the index would not limit the number of rows.

But in The Slow Query Log(https://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html), I see the following statement:
The query must have taken at least long_query_time seconds, or log_queries_not_using_indexes must be enabled and the query used no indexes for row lookups.

I think this statement is inconsistent and confusing to the reader.

How to repeat:
This is a problem about documentation.

Suggested fix:
I suggest to change The Slow Query Log(https://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html) statement as follows:

The query must have taken at least long_query_time seconds, or log_queries_not_using_indexes must be enabled and the query used no indexes or used index would not limit the number of rows.

Hi Mr. zhang,

Thank you for your bug report.

We agree fully with your idea on changing our documentation on this issue.

This is now a verified Documentation bug report.

Thanks! I'll try to take a look at this soon.

Thanks, Jon ......