Author: jstephens
Date: 2010-03-19 11:44:40 +0100 (Fri, 19 Mar 2010)
New Revision: 19597
Log:
Revised BUG#48846 changelog entry (Thanks, James!)
Modified:
trunk/dynamic-docs/changelog/mysqld-2.xml
Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml 2010-03-18 20:31:17 UTC (rev 19596)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml 2010-03-19 10:44:40 UTC (rev 19597)
Changed blocks: 3, Lines Added: 10, Lines Deleted: 3; 1702 bytes
@@ -30,7 +30,7 @@
<para>
When performing a complex mix of node restarts and system
restarts, the node that was elected as master sometimes required
- optimized node-recovery due to missing <literal>REDO</literal>
+ optimized node recovery due to missing <literal>REDO</literal>
information. When this happened, the node crashed with
<errortext>Failure to recreate object ... during restart, error
721</errortext> (because the <literal>DBDICT</literal> restart
@@ -3501,7 +3501,9 @@
<tags>
<highlight type="partitioning"/>
+ <highlight type="performance"/>
<manual type="optimization"/>
+ <manual type="records_in_range"/>
<manual type="pruning"/>
</tags>
@@ -3521,8 +3523,13 @@
<para>
When used on partitioned tables, the
- <literal>records_in_range</literal> handler call checked all
- partitions, rather than the unpruned partitions only.
+ <literal>records_in_range</literal> handler call checked more
+ partitions than necessary. The fix for this issue reduces the
+ number of unpruned partitions checked for statistics in
+ partition range checking, which has resulted in some partition
+ operations being performed up to 2-10 times faster than before
+ this change was made, when testing with tables having 1024
+ partitions.
</para>
</message>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r19597 - trunk/dynamic-docs/changelog | jon.stephens | 19 Mar |
