Plan-scoring changes for multiplanning DISTINCT_SCAN

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • Fully Compatible
    • QO 2024-11-25, QO 2024-12-09, QO 2024-12-23
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We may need to implement additional tie-breaking for a case where an index scan and a distinct scan both scan the same number of keys, in order to favour the DISTINCT_SCAN. This ticket encompasses testing such cases/ potentially making this & additional fixes needed for the resulting tests.

            Assignee:
            Daniel Segel
            Reporter:
            Alya Berciu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: