Bug #38703 Change the min value for long_query_time from 1 to 0

Submitted:	10 Aug 2008 18:02	Modified:	22 Jun 2010 8:44
Reporter:	Mark Callaghan	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server: Logging	Severity:	S4 (Feature request)
Version:	5.0	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	log, long_query_time, query, slow

Description:
This has been added to 5.1.

The min value for long_query_time is 1 in MySQL 5.0. Therefore, I can't use the slow query log to log all queries over a short period of time. This is very useful to do when monitoring workloads.

How to repeat:
NA

Suggested fix:
Change the min value in mysqld.cc to be 0

  {"long_query_time", OPT_LONG_QUERY_TIME,
   "Log all queries that have taken more than long_query_time seconds to execute to file.",
   (gptr*) &global_system_variables.long_query_time,
   (gptr*) &max_system_variables.long_query_time, 0, GET_ULONG,
   REQUIRED_ARG, 10, 1, LONG_TIMEOUT, 0, 1, 0},

Verified as described with 5.0 bzr tree.

This is only in 5.0.

The fix should be:

{"long_query_time", OPT_LONG_QUERY_TIME,
   "Log all queries that have taken more than long_query_time seconds to execute to
file.",
   (gptr*) &global_system_variables.long_query_time,
   (gptr*) &max_system_variables.long_query_time, 0, GET_ULONG,
   REQUIRED_ARG, 10, 0, LONG_TIMEOUT, 0, 1, 0},

Due to 5.0 now being in extended support, bug status seems wrong, setting to wont fix.

Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.