diff --git a/sql/opt_range.cc b/sql/opt_range.cc
index 04842374ae1..faeafab7209 100644
--- a/sql/opt_range.cc
+++ b/sql/opt_range.cc
@@ -5711,8 +5711,7 @@ ROR_SCAN_INFO *make_ror_scan(const PARAM *param, int idx, SEL_ARG *sel_arg)
       bitmap_set_bit(&ror_scan->covered_fields, key_part->fieldnr-1);
   }
   ror_scan->index_read_cost=
-    param->table->file->keyread_time(ror_scan->keynr, 1,
-                                     param->table->quick_rows[ror_scan->keynr]);
+    param->table->file->keyread_time(ror_scan->keynr, 1, ror_scan->records);
   DBUG_RETURN(ror_scan);
 }
 
diff --git a/sql/opt_range.h b/sql/opt_range.h
index 1a0a2ee0029..23533578b91 100644
--- a/sql/opt_range.h
+++ b/sql/opt_range.h
@@ -515,8 +515,7 @@ public:
     Current implementation doesn't detect all cases where index merge could
     be used, in particular:
 
-     * index merge+'using index' is not supported (this the consequence of
-       the above restriction)
+     * index_merge+'using index' is not supported
 
      * If WHERE part contains complex nested AND and OR conditions, some ways
        to retrieve rows using index merge will not be considered. The choice