Bug #39618 Using log-short-format does not change what is logged
Submitted: 23 Sep 2008 21:56 Modified: 26 Nov 2008 16:55
Reporter: Donna Harmon Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Logging Severity:S3 (Non-critical)
Version:5.0.27, 5.0.67 OS:Microsoft Windows (XP)
Assigned to: CPU Architecture:Any
Triage: Triaged: D3 (Medium)

[23 Sep 2008 21:56] Donna Harmon
Description:
The reference manual states "log-short-format - Log less information to the update log, binary update log, and slow query log, if they have been activated. For example, the username and timestamp are not logged for queries."

However, when this option is set there is no change to what is logged in the slow query log or binary log (the username and timestampe are still logged)

How to repeat:
Run slow query, check slow query log and binary log, turn on log-short-format, run slow query and check slow query log and binary log
[23 Sep 2008 22:06] Miguel Solorzano
Thank you for the bug report. Your version is quite older could you please test with the latest released version 5.0.67. Thanks in advance.
[23 Sep 2008 22:16] Donna Harmon
http://dev.mysql.com/doc/refman/5.0/en/server-options.html
[23 Sep 2008 22:29] Donna Harmon
Slow Query Log with log-short-format enabled:
----------------------------------------------
C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt, Version: 5.0.27-community-nt-log. started with:
TCP Port: 3306, Named Pipe: (null)
Time                 Id Command    Argument
# Time: 080923 17:21:23
# User@Host: root[root] @ localhost [127.0.0.1]
# Query_time: 0  Lock_time: 0  Rows_sent: 6  Rows_examined: 6
use default;
SHOW FULL COLUMNS FROM `zipcodes`.`zipcodes`;
# Time: 080923 17:21:24
# User@Host: root[root] @ localhost [127.0.0.1]
# Query_time: 1  Lock_time: 0  Rows_sent: 42192  Rows_examined: 42192
SELECT * FROM `zipcodes`.`zipcodes`;

Slow Query Log with log-short-format disabled:
----------------------------------------------
C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt, Version: 5.0.27-community-nt-log. started with:
TCP Port: 3306, Named Pipe: (null)
Time                 Id Command    Argument
# Time: 080923 17:22:21
# User@Host: root[root] @ localhost [127.0.0.1]
# Query_time: 0  Lock_time: 0  Rows_sent: 6  Rows_examined: 6
use default;
SHOW FULL COLUMNS FROM `zipcodes`.`zipcodes`;
# User@Host: root[root] @ localhost [127.0.0.1]
# Query_time: 0  Lock_time: 0  Rows_sent: 42192  Rows_examined: 42192
SELECT * FROM `zipcodes`.`zipcodes`;
[23 Sep 2008 22:36] Todd Farmer
Verified as reported in 5.0.67.
[26 Nov 2008 16:38] Paul Dubois
This is a server bug. Or if it's not, could a developer please specify the expected behavior so that the documentation can be updated correctly? Thanks.

Changing category to Server: Tracing and Logging