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

Improve optimizer cost model to take ICP cost (and benefits) into account

    XMLWordPrintable

Details

    • Task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • Optimizer
    • None

    Description

      Currently optimizer does not take ICP benefits into account and this may lead to suboptimal index choice (see MDEV-29151 for the related examples and discussion), while forcing the index that can be used for ICP provides a notably faster execution for the query.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29151 Index choice depends on index definition order

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

          Task - A task that needs to be done. MDEV-29121 Optimizer does not use the index for SELECT while it gives notable improvement in the execution time when FORCEd

          • Major - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              valerii Valerii Kravchuk
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.