Multiplan both DISTINCT_SCAN and IXSCAN on same index together

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This is a tricky one, because our current productivity scoring calculation would favor an index scan. However, an index scan is probably a better choice than a distinct scan for keys that have few/no duplicates, because we don't seek for every key (we just scan). This will require some benchmarking work to confirm as well.

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

              Created:
              Updated: