Cap $in length in plan cache key with internalQueryMaxScansToExplode + 1

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.1, 7.3.0-rc0, 7.0.5
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v7.2, v7.0
    • QE 2023-12-11
    • 35
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The reason we add $in length to plan cache key is possible explodeForSort optimization.

      We have internalQueryMaxScansToExplode query knob that limits the maximum number of explode for sort index scans. 

      We can use it to limit the number of plan cache entries.

              Assignee:
              Ivan Fefer
              Reporter:
              Ivan Fefer
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: