Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
https://mariadb.com/kb/en/slow-query-log-overview/#logging-queries-that-examine-a-minimum-row-limit
STATES: "The slow query log can be configured to log queries that examine a minimum number of rows regardless of their execution time by setting the min_examined_row_limit system variable."
It does not work like this. It does not trigger a logging when more rows than this number are examined.
https://mariadb.com/docs/server/ref/mdb/system-variables/min_examined_row_limit/
STATES "Don't write queries to slow log that examine fewer rows than that"
That is the way it actually behaves. It works like a floor. If a query is slower than long_query_time AND ALSO examines more rows than min_examined_row_limit it will be logged.
So, which is correct?
We must either
- fix min_examined_row_limit to work like KB documentation and change Enterprise documentation
- we must fix KB documentation to match Enterprise Documentation