From: Jorgen Loland
Date: January 18 2011 3:20pm
Subject: bzr push into mysql-next-mr-bugfixing branch (jorgen.loland:3259 to 3260)
 WL#5594
List-Archive: http://lists.mysql.com/commits/129100
Message-Id: <20110118152042.EE55D8B3@atum21.norway.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

 3260 Jorgen Loland	2011-01-18
      WL#5594: Add optimizer traces to the range optimizer
      
      Review comments: fix documentation for SQL_SELECT::traced_before 

    modified:
      sql/opt_range.h
 3259 Guilhem Bichot	2011-01-18
      adjust threshold in test

    modified:
      mysql-test/include/optimizer_trace.inc
      mysql-test/r/optimizer_trace_no_prot.result
      mysql-test/r/optimizer_trace_ps_prot.result
=== modified file 'sql/opt_range.h'
--- a/sql/opt_range.h	2011-01-14 15:53:48 +0000
+++ b/sql/opt_range.h	2011-01-18 15:20:27 +0000
@@ -857,10 +857,13 @@ class SQL_SELECT :public Sql_alloc {
   bool	free_cond;
 
   /** 
-      Used by optimizer tracing if this is a subquery: Whether or not
-      execution of this subselect has been traced by optimizer tracing
-      already. If optimizer trace option DYNAMIC_RANGE is disabled,
-      this is used to disable tracing after the first one.
+    Used for QS_DYNAMIC_RANGE, i.e., "Range checked for each record".
+    Used by optimizer tracing to decide whether or not dynamic range
+    analysis of this select has been traced already. If optimizer
+    trace option DYNAMIC_RANGE is enabled, range analysis will be
+    traced with different ranges for every record to the left of this
+    table in the join. If disabled, range analysis will only be traced
+    for the first range.
   */
   bool traced_before;
 

No bundle (reason: useless for push emails).