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

optimizer trace

    XMLWordPrintable

Details

    Description

      In MySQL, Optimizer trace is a JSON object recording the execution path through the optimizer, decisions that were made and the reasons for them. See https://dev.mysql.com/doc/internals/en/optimizer-tracing.html

      Users were asking for MariaDB to have a similar feature.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-7239 explain index choice

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          includes

          Task - A task that needs to be done. MDEV-17929 Optimizer trace support for different parts of the server

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-17930 Optimizer trace: what's on the execution path when trace=off?

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18117 Crash with Explain extended when using limit rows examined

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-18172 Benchmarking 10.4 for optimizer trace

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18306 Optimizer_trace has invalid JSON near rows_estimation

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-18489 Limit the memory used by the optimizer trace

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

          Task - A task that needs to be done. MDEV-12980 Index hints for loose scan

          • Major - Major loss of function.
          • Confirmed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18670 Document optimizer trace

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-20440 Optimizer trace: print more details about semi-join optimization

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18527 Optimizer trace for DELETE query shows table:null

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18528 Optimizer trace support for multi-table UPDATE and DELETE

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18741 Optimizer trace: multi-part key ranges are printed incorrectly.

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-18822 investigate performance regressions in 10.4

          • Major - Major loss of function.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MDEV-19160 JSON_DETAILED output unnecessarily verbose (Part Time project)

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-20444 More information regarding access of a table to be printed inside the optimizer_trace

          • Major - Major loss of function.
          • Closed

          Activity

            People

              varun Varun Gupta (Inactive)
              serg Sergei Golubchik
              Votes:
              10 Vote for this issue
              Watchers:
              17 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.