summaryrefslogtreecommitdiff
path: root/sql/ha_innodb.cc
diff options
context:
space:
mode:
authortsmith@sita.local <>2007-10-02 23:47:30 -0600
committertsmith@sita.local <>2007-10-02 23:47:30 -0600
commit0111438b450bd08ac98eaab2b780815a28a6c7ea (patch)
tree56780d03bca97d190842d738e7b1fc9bec6eab74 /sql/ha_innodb.cc
parentba419bdc8c690e2a328f35f70df89936e030f481 (diff)
downloadmariadb-git-0111438b450bd08ac98eaab2b780815a28a6c7ea.tar.gz
Bug #20358: InnoDB hang on the adaptive hash index latch in btr0sea.c
Add --skip-innodb-adaptive-hash-index option, which is a way to work around the bug (by disabling the adaptive hash feature entirely). This may be useful even once the bug is fixed, for benchmarking purposes. There are some workloads for which the adaptive hash index is not effective.
Diffstat (limited to 'sql/ha_innodb.cc')
-rw-r--r--sql/ha_innodb.cc3
1 files changed, 3 insertions, 0 deletions
diff --git a/sql/ha_innodb.cc b/sql/ha_innodb.cc
index 2d47c42cf1d..86d3e930122 100644
--- a/sql/ha_innodb.cc
+++ b/sql/ha_innodb.cc
@@ -174,6 +174,7 @@ my_bool innobase_file_per_table = FALSE;
my_bool innobase_locks_unsafe_for_binlog = FALSE;
my_bool innobase_rollback_on_timeout = FALSE;
my_bool innobase_create_status_file = FALSE;
+my_bool innobase_adaptive_hash_index = TRUE;
static char *internal_innobase_data_file_path = NULL;
@@ -1376,6 +1377,8 @@ innobase_init(void)
srv_use_doublewrite_buf = (ibool) innobase_use_doublewrite;
srv_use_checksums = (ibool) innobase_use_checksums;
+ srv_use_adaptive_hash_indexes = (ibool) innobase_adaptive_hash_index;
+
os_use_large_pages = (ibool) innobase_use_large_pages;
os_large_page_size = (ulint) innobase_large_page_size;