COUNT_SCAN candidate plans should be evaluated with the multi-planner

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently when count query has a filter and there is an index The oldest index that has the prefix of the filter is picked. Yet this is not always optimal as there can be a smaller index which would require less scanning steps within the index. Distinct already implements a similar approach. The task here is to implement a similar selection method for count.

              Assignee:
              Unassigned
              Reporter:
              Peter Volk
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: