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

Document deprecation/removal of innodb_lock_schedule_algorithm

Details

    Description

      When MDEV-16664 is closed, we should document the deprecation/removal of innodb_lock_schedule_algorithm.

      Attachments

        Issue Links

          Activity

            Due to the regression MDEV-16664 (potential corruption due to wrongly granting exclusive locks on the same record to more than one active transaction at a time), I did the following:

            1. Reverted the default back to the safe value
            2. Added a deprecation and corruption warning
            3. Removed the option innodb_lock_schedule_algorithm and related code (MariaDB Server 10.6) that had been added in MDEV-11039.
            marko Marko Mäkelä added a comment - Due to the regression MDEV-16664 (potential corruption due to wrongly granting exclusive locks on the same record to more than one active transaction at a time), I did the following: Reverted the default back to the safe value Added a deprecation and corruption warning Removed the option innodb_lock_schedule_algorithm and related code (MariaDB Server 10.6) that had been added in MDEV-11039 .
            GeoffMontee Geoff Montee (Inactive) added a comment - Documented here: https://mariadb.com/kb/en/innodb-system-variables/#innodb_lock_schedule_algorithm

            People

              GeoffMontee Geoff Montee (Inactive)
              GeoffMontee Geoff Montee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.