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

Optimizer does not identify index as covering on myisam table

    XMLWordPrintable

Details

    Description

      In some cases optimizer fetches full rows even when the index used covers the entire query. The index-only plan is used when the index is forced by USE/FORCE INDEX() hint. If the order of columns in the index is changed, the query is executed index-only without the hint (but in the test case that leads to filesort).

      Affects MySQL too (tested 5.6, probably others), reported as http://bugs.mysql.com/bug.php?id=81601

      Attachments

        Activity

          People

            serg Sergei Golubchik
            jkavalik Jiri Kavalik
            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.