MySQL Bugs: #35731: Documentation of min-examined-row-limit off

Bug #35731	Documentation of min-examined-row-limit off
Submitted:	1 Apr 2008 5:18	Modified:	2 Apr 2008 23:06
Reporter:	Glynn Durham	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.1.21	OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any
Tags:	min-examined-row-limit

Description:
The online MySQL 5.1 reference guide, section 5.1.2, says of min-examined-row-limit: "When this option is set, queries which examine fewer than number rows are not written to the query log. The default is 0. "  Change "query log" to "slow query log".

How to repeat:
This is a documentation bug.  To repeat the actual behavior of the server, start a server with 
[mysqld]
log-slow-queries=slow.log
log = general.log
log-queries-not-using-indexes
min-examined-row-limit = 1000

Then, in a session against the world database, issue statement 1:
select * from city limit 1001;

, statement 2:
select * from city limit 999;

Both queries are logged in the general log, but only statement 1 is logged in the slow query log.  Therefore, the value of min-examined-row-limit affects what hits the slow query log, *not* what hits the query log.  

Suggested fix:
In all documented definitions of the new variable "min-examined-row-limit", change "query log" to "slow query log".

Thank you for the bug report. Verified as described.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.