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

New defaults for eq_range_index_dive_limit in 10.4

Details

    Description

      See https://lists.launchpad.net/maria-developers/msg11460.html :

      So, MDEV-16934 introduced eq_range_index_dives_limit into 10.2.8 and 10.3.0.

      The default was set to 0 (which means no limit) in order to not introduce
      optimizer behavior changes into stable versions.

      The question is: should 10.4 also have 0 by default or we can set it to some
      finite limit? MySQL's default value is 10.

      After the decision was: It should be set to 10. This is what this task is about.

      Saw MYSQL 8.0 , the default there is 200
      https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_eq_range_index_dive_limit
      psergey igor for your information

      Attachments

        Issue Links

          Activity

            Ok to push the patch

            psergei Sergei Petrunia added a comment - Ok to push the patch

            greenman on the optimizer call we came to the conclusion that we will change the value to 200 instead of 10. The reason to change the value was to have something greater than 0 atleast

            varun Varun Gupta (Inactive) added a comment - greenman on the optimizer call we came to the conclusion that we will change the value to 200 instead of 10. The reason to change the value was to have something greater than 0 atleast

            People

              varun Varun Gupta (Inactive)
              psergei Sergei Petrunia
              Votes:
              0 Vote for this issue
              Watchers:
              7 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.