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

Set innodb_snapshot_isolation=ON by default

    XMLWordPrintable

Details

    Description

      From the very beginning, the default InnoDB transaction isolation level REPEATABLE READ does not correspond to any established definition. The main issue is the lack of write/write conflict detection. To fix that and to make REPEATABLE READ correspond to Snapshot Isolation, we introduced the Boolean session variable innodb_snapshot_isolation in MariaDB Server 10.6.18, 10.11.8, 11.4.2. It is disabled by default in order not to break any user applications.

      In a new major version of MariaDB Server, we had better enable this parameter by default, so that bugs like MDEV-26642, MDEV-26643, MDEV-32898 will be avoided by default.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35488 innodb_snapshot_isolation is ON by default in 11.6+

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35647 Assertion `!have_any()' failed in srw_lock_debug::rd_lock

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26642 Weird SELECT view when a record is modified to the same value by two transactions

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26643 Inconsistent behaviors of UPDATE under RU & RC isolation level

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32898 Phantom rows caused by UPDATE of PRIMARY KEY

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35140 Support innodb-snapshot-isolation in Galera cluster

          • Major - Major loss of function.
          • In Progress

          Activity

            People

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