summaryrefslogtreecommitdiff
path: root/storage/innobase/include/sync0sync.h
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2020-12-03 14:17:22 +0200
committerMarko Mäkelä <marko.makela@mariadb.com>2020-12-03 15:27:50 +0200
commitac028ec5d853a4f797e5c48c348959618c773d62 (patch)
tree5d013c144b333cefedad8999e929dc97cf476b47 /storage/innobase/include/sync0sync.h
parent06efef4be39a415cc9c183066dfbe73ab5dc0866 (diff)
downloadmariadb-git-ac028ec5d853a4f797e5c48c348959618c773d62.tar.gz
MDEV-24142: Remove the LatchDebug interface to rw-locks
The latching order checks for rw-locks have not caught many bugs in the past few years and they are greatly complicating the code. Last time the debug checks were useful was in commit 59caf2c3c1fe128d1d2c3a8df9fadd4d25ab7102 (MDEV-13485). The B-tree hang MDEV-14637 was not caught by LatchDebug, because the granularity of the checks is not sufficient to distinguish the levels of non-leaf B-tree pages. The interface was already made dead code by the grandparent commit 03ca6495df31313c96e38834b9a235245e2ae2a8.
Diffstat (limited to 'storage/innobase/include/sync0sync.h')
-rw-r--r--storage/innobase/include/sync0sync.h3
1 files changed, 0 insertions, 3 deletions
diff --git a/storage/innobase/include/sync0sync.h b/storage/innobase/include/sync0sync.h
index d1e727c4777..ab83e55f279 100644
--- a/storage/innobase/include/sync0sync.h
+++ b/storage/innobase/include/sync0sync.h
@@ -64,9 +64,6 @@ extern mysql_pfs_key_t rtr_path_mutex_key;
extern mysql_pfs_key_t redo_rseg_mutex_key;
extern mysql_pfs_key_t noredo_rseg_mutex_key;
extern mysql_pfs_key_t page_zip_stat_per_index_mutex_key;
-# ifdef UNIV_DEBUG
-extern mysql_pfs_key_t rw_lock_debug_mutex_key;
-# endif /* UNIV_DEBUG */
extern mysql_pfs_key_t srv_innodb_monitor_mutex_key;
extern mysql_pfs_key_t srv_misc_tmpfile_mutex_key;
extern mysql_pfs_key_t srv_monitor_file_mutex_key;