Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-86639

Improve index deduplication logic

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • QO 2024-04-01, QO 2024-04-15, QO 2024-04-29, QO 2024-05-13, QO 2024-05-27

      SERVER-82677 deduplicated indexes in straightforward and safe situations. The requirements were strict, for example if there's a shard key we wouldn't consider deduping. Or if the compared indexes were not plain indexes (not partial/unique/sparse/collated or any type other than btree) we would skip deduplication.

       

      This tickets goal is to improve this logic to deduplicate in more scenarios. We should be careful to only dedup when we know the plans are guaranteed to perform equally well or one strictly worse than the other.

            Assignee:
            Unassigned Unassigned
            Reporter:
            matt.boros@mongodb.com Matt Boros
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: