Bug #14384 5.0 Upgrade page needs to mention change in behaviour of slow log

• Submitted: 27 Oct 2005 10:29
• Modified: 27 Oct 2005 19:31
• Reporter: Tobias Asplund
• Status: Not a Bug
• Category: MySQL Server: Documentation
• Severity: S2 (Serious)
• Version: 5.0.x
• CPU Architecture: Any

[27 Oct 2005 10:29] Tobias Asplund

Description:
The slow log now in 5.0 automatically enables --log-queries-not-using-indexes.
When people having the old slow log turned on, and upgrading may now find themselves with slow logs growing gigabytes a day.
This is serious enough to mention on the upgrade page so that they can disable this behaviour if needed.

http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html

How to repeat:
(need to type something here)

[27 Oct 2005 19:31] Stefan Hinz

I cannot confirm the described behaviour. Testing with MySQL 5.0.15, I turned on the slow query log, then issued some queries that didn't use indexes: They weren't log. I had to explicitly specify log-queries-not-using-indexes to make the server log queries that didn't use indexes. This is behaviour as documented.

[27 Oct 2005 21:04] Tobias Asplund

In MySQL 5.0's slow query log, slow queries that do not use indexes are logged as well as those that do. To prevent queries that do not use indexes from being logged in the slow query log, use the --log-short-format option. 

From:
http://dev.mysql.com/doc/refman/5.0/en/slow-query-log.html

There's an inconsistency somewhere, either in the behaviour of the default slow-log behaviour or the manual.

I'm sorry if I'm wrong, but that's how I read it here.