Author: jstephens
Date: 2007-11-05 17:50:32 +0100 (Mon, 05 Nov 2007)
New Revision: 8533
Log:
Documented fix for Bug #25412 (?\206?\188sec resolution for long_query_time when
logging to files) (Leith)
Modified:
trunk/dynamic-docs/changelog/mysqld.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-6.0/dba-core.xml
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-05 16:21:46 UTC (rev 8532)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-05 16:50:32 UTC (rev 8533)
Changed blocks: 1, Lines Added: 30, Lines Deleted: 0; 1054 bytes
@@ -6,6 +6,36 @@
]>
<changelog>
+ <logentry entrytype="feature">
+
+ <bugs>
+ <fixes bugid="25412"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.21"/>
+ <version ver="6.0.4"/>
+ </versions>
+
+ <message>
+
+ <para>
+ It is now possible to set <literal>long_query_time</literal> in
+ microseconds or to 0. Setting this value to 0 causes all queries
+ to be recorded in the slow query log.
+ </para>
+
+ <para>
+ Currently, fractional values can be used only when logging to
+ files. We plan to provide this functionality for logging to
+ tables when time-related data types are enhanced to support
+ microsecond resolution.
+ </para>
+
+ </message>
+
+ </logentry>
+
<logentry entrytype="bug">
<tags>
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2007-11-05 16:21:46 UTC (rev 8532)
+++ trunk/refman-5.1/dba-core.xml 2007-11-05 16:50:32 UTC (rev 8533)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 2; 1152 bytes
@@ -5518,8 +5518,13 @@
logged to the slow query log file. This value is measured
in real time, not CPU time, so a query that is under the
threshold on a lightly loaded system might be above the
- threshold on a heavily loaded one. The minimum value is 1.
- The default is 10. See <xref linkend="slow-query-log"/>.
+ threshold on a heavily loaded one. Prior to MySQL 5.1.21,
+ the minimum value is 1, and the value set for this
+ variable must be an integer. Beginning with MySQL 5.1.21,
+ the default is 0, and a resolution of microseconds is
+ supported when logging to a file — however, only
+ integer values may be used when logging to tables. The
+ default value is 10. See <xref linkend="slow-query-log"/>.
</para>
</listitem>
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2007-11-05 16:21:46 UTC (rev 8532)
+++ trunk/refman-6.0/dba-core.xml 2007-11-05 16:50:32 UTC (rev 8533)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 2; 1150 bytes
@@ -5355,8 +5355,13 @@
logged to the slow query log file. This value is measured
in real time, not CPU time, so a query that is under the
threshold on a lightly loaded system might be above the
- threshold on a heavily loaded one. The minimum value is 1.
- The default is 10. See <xref linkend="slow-query-log"/>.
+ threshold on a heavily loaded one. Prior to MySQL 6.0.4,
+ the minimum value is 1, and the value set for this
+ variable must be an integer. Beginning with MySQL 6.0.4,
+ the default is 0, and a resolution of microseconds is
+ supported when logging to a file — however, only
+ integer values may be used when logging to tables. The
+ default value is 10. See <xref linkend="slow-query-log"/>.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8533 - in trunk: dynamic-docs/changelog refman-5.1 refman-6.0 | jon | 5 Nov |
