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

Partition Pruning not included in optimizer tracing

    XMLWordPrintable

Details

    Description

      There is a feature called "Partition Pruning" ( entry point:
      prune_partitions()) where the optimizer figures out the set of
      partitions it will need to read for a given table when running the
      query.

      One can see its result in "partitions" column in EXPLAIN PARTITIONS or
      in EXPLAIN FORMAT=JSON.

      Nothing is printed in the optimizer trace about this.

      Attachments

        1. Notes
          6 kB
          Rex Johnston
        2. partition_pruning.out
          0.9 kB
          Rex Johnston
        3. partition_pruning.sql
          2 kB
          Rex Johnston

        Issue Links

          Activity

            People

              psergei Sergei Petrunia
              Johnston Rex Johnston
              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.