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

Do not acquire InnoDB record locks when covering table locks exist

    XMLWordPrintable

Details

    Description

      InnoDB is unnecessarily acquiring record locks when the transaction is already holding a table lock that prevents any conflicts. Starting with MySQL 4.0 or 4.1, the table locks acquired by LOCK TABLES are mapped to shared or exclusive InnoDB table locks, but InnoDB is still acquiring unnecessary record locks internally.

      The attached patch is only a start. It adjusts a debug check so that exclusive or shared table locks are considered to be equivalent to exclusive or shared record locks.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16675 Unnecessary explicit lock acquisition during UPDATE or DELETE

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-24813 Locking full table scan fails to use table-level locking

          • Critical - Crashes, loss of data, severe memory leak.
          • In Review

          Task - A task that needs to be done. MDEV-11215 Several locks taken to same record inside a transaction.

          • Major - Major loss of function.
          • Stalled

          Activity

            People

              vlad.lesin Vladislav Lesin
              marko Marko Mäkelä
              Votes:
              2 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.