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

Deprecate the parameter innodb_change_buffering

Details

    Description

      As a follow-up to MDEV-27734 Set innodb_change_buffering=none by default
      we should mark the option innodb_change_buffering deprecated, to inform users of its future removal.

      To allow seamless upgrades, we must retain some traces of the change buffering even after ignoring the option. Any buffered changes must continue to be merged when the affected secondary index leaf pages are being accessed.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-29694 Remove the InnoDB change buffer

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

          Task - A task that needs to be done. MDEV-27734 Set innodb_change_buffering=none by default

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

          New Feature - A new feature of the product, which has yet to be developed. MDEV-11658 Simpler, faster IMPORT of InnoDB tables

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

          Task - A task that needs to be done. MDEV-29983 Deprecate innodb_file_per_table

          • 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-30134 buf_page_t::unfix(): Assertion `!((f ^ (f - 1)) & LRU_MASK)' failed

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-31088 Server freeze due to innodb_change_buffering and innodb_file_per_table=0

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30332 PLUGIN_VAR_DEPRECATED fails to throw a warning on startup

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

          Activity

            Ascending order - Click to sort in descending order
            marko Marko Mäkelä created issue -
            marko Marko Mäkelä made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            Priority Major [ 3 ] Blocker [ 1 ]
            marko Marko Mäkelä made changes -
            issue.field.resolutiondate 2022-02-14 08:30:56.0 2022-02-14 08:30:56.912
            marko Marko Mäkelä made changes -
            Fix Version/s 10.9.0 [ 27113 ]
            Fix Version/s 10.9 [ 26905 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -

            People

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