summaryrefslogtreecommitdiff
path: root/storage
diff options
context:
space:
mode:
authorAnnamalai Gurusami <annamalai.gurusami@oracle.com>2012-06-01 14:12:57 +0530
committerAnnamalai Gurusami <annamalai.gurusami@oracle.com>2012-06-01 14:12:57 +0530
commita28a2ca798e8a4912cf1b91b6e71eaa0a9fb8bb7 (patch)
tree48e569e721d18091ea8691dd5130ec69e5adf39a /storage
parent2ebd927ec0ba2de6219dc23a01c3988273302b3e (diff)
downloadmariadb-git-a28a2ca798e8a4912cf1b91b6e71eaa0a9fb8bb7.tar.gz
Bug #13933132: [ERROR] GOT ERROR -1 WHEN READING TABLE APPEARED
WHEN KILLING Suppose there is a query waiting for a lock. If the user kills this query, then "Got error -1 when reading table" error message must not be logged in the server log file. Since this is a user requested interruption, no spurious error message must be logged in the server log. This patch will remove the error message from the log. approved by joh and tatjana
Diffstat (limited to 'storage')
-rw-r--r--storage/innobase/handler/ha_innodb.cc1
1 files changed, 1 insertions, 0 deletions
diff --git a/storage/innobase/handler/ha_innodb.cc b/storage/innobase/handler/ha_innodb.cc
index 8ed082037f0..51b7007145c 100644
--- a/storage/innobase/handler/ha_innodb.cc
+++ b/storage/innobase/handler/ha_innodb.cc
@@ -4893,6 +4893,7 @@ ha_innobase::index_read(
ulint ret;
DBUG_ENTER("index_read");
+ DEBUG_SYNC_C("ha_innobase_index_read_begin");
ut_a(prebuilt->trx == thd_to_trx(user_thd));
ut_ad(key_len != 0 || find_flag != HA_READ_KEY_EXACT);