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

Remove innodb_locks_unsafe_for_binlog

    XMLWordPrintable

Details

    Description

      The parameter innodb_locks_unsafe_for_binlog was deprecated in MariaDB 10.0. Let us finally remove it.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-24224 Gap lock on delete in 10.5 using READ COMMITTED

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-19563 Galera depends on deprecated option innodb_locks_unsafe_for_binlog

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21822 InnoDB: Failing assertion: UT_LIST_GET_LEN(trx->lock.trx_locks) == 0 upon trivial SELECT from InnoDB table after wrong operations with sequences

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-18650 Options deprecated in previous versions

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20605 Awaken transaction can miss inserted by other transaction records due to wrong persistent cursor restoration

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

          Activity

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.