diff options
author | Annamalai Gurusami <annamalai.gurusami@oracle.com> | 2011-12-13 14:26:12 +0530 |
---|---|---|
committer | Annamalai Gurusami <annamalai.gurusami@oracle.com> | 2011-12-13 14:26:12 +0530 |
commit | ad84fb5c3763b3a5c6c2146c8fc824f0d385c77c (patch) | |
tree | 4b138d70eef355c219802832404be884c1e44ea5 /mysql-test/suite/ndb/r/ndb_bug26793.result | |
parent | 3d58fd6900128503d8516515496868c516ce63a0 (diff) | |
download | mariadb-git-ad84fb5c3763b3a5c6c2146c8fc824f0d385c77c.tar.gz |
Bug #13117023: Innodb increments handler_read_key when it should not
The counter handler_read_key (SSV::ha_read_key_count) is incremented
incorrectly.
The mysql server maintains a per thread system_status_var (SSV)
object. This object contains among other things the counter
SSV::ha_read_key_count. The purpose of this counter is to measure the
number of requests to read a row based on a key (or the number of
index lookups).
This counter was wrongly incremented in the
ha_innobase::innobase_get_index(). The fix removes
this increment statement (for both innodb and innodb_plugin).
The various callers of the innobase_get_index() was checked to
determine if anybody must increment this counter (if they first call
innobase_get_index() and then perform an index lookup). It was found
that no caller of innobase_get_index() needs to worry about the
SSV::ha_read_key_count counter.
Diffstat (limited to 'mysql-test/suite/ndb/r/ndb_bug26793.result')
0 files changed, 0 insertions, 0 deletions