Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-33150

double-locking of LOCK_thd_kill in performance_schema.session_status

    XMLWordPrintable

Details

    Description

      --source include/have_innodb.inc
       
      SELECT table_catalog,table_schema,table_name,index_schema,index_name FROM information_schema.statistics;
      SET max_session_mem_used=32768;
      --ERROR ER_OPTION_PREVENTS_STATEMENT
      SELECT * FROM performance_schema.session_status;
      SET GLOBAL innodb_io_capacity_max=100;
      

      Leads to

      11.4.0 3fad2b115569864d8c1b7ea90ce92aa895cfef08 (Debug)

      safe_mutex: Found wrong usage of mutex 'LOCK_global_system_variables' and 'LOCK_thd_kill'
      Mutex currently locked (in reverse order):
      LOCK_thd_kill                     /test/mtest/11.4_dbg/sql/sql_class.h  line 4703
      LOCK_global_system_variables      /test/mtest/11.4_dbg/sql/sys_vars_shared.h  line 56
      

      Attachments

        Issue Links

          Activity

            People

              serg Sergei Golubchik
              ramesh Ramesh Sivaraman
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.