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

Optimizer trace doesn't cover LATERAL DERIVED

    XMLWordPrintable

Details

    Description

      Optimizer trace doesn't mention LATERAL DERIVED optimization. This can be extra confusing because LATERAL DERIVED code invokes parts of join optimizer that do the tracing.

      This task is about

      • figuring out what to trace/log
      • do it.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-30876 Back port LATERAL DERIVED coverage in optimizer trace

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26300 LATERAL DERIVED: Optimizer trace insufficient, odd computations

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

          Activity

            People

              psergei Sergei Petrunia
              psergei Sergei Petrunia
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 1.5h
                  1.5h

                  Git Integration

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