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

Encapsulate calculations of the table access cost and make them consistent and tunable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      This task is mostly a re-engineering task.
      Currently when calculating the cost of a ref table access method the function best_access_path makes an assumption that any index look-up is performed into a B-tree and the function uses engine independent code for this calculations.
      The cost calculations also use some constants that should be done tunable through system variables since these constants may be different for different platform/environments.

      This task is implemented in preparation for the development that will support more realistic cost model for query execution plans.

      [1] http://askmonty.org/worklog/?tid=251

        Gliffy Diagrams

          Attachments

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                igor Igor Babaev
                Reporter:
                igor Igor Babaev
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 week, 2 days, 4 hours, 30 minutes
                  1w 2d 4h 30m