Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- auto-reverted
- quick-win

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Linked BF Score:
200
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Due to SERVER-97217, AND_SORTED plans are never chosen by the multi-planner in practice. This means we should either change multi-planner scoring (do SERVER-97217), which is risky, or just reduce multi-planner wastework by disabling these plans in plan enumeration.

blocks

SERVER-108593 Run the plan_stability tests with internalQueryPlannerEnableSortIntersection

Needs Scheduling

is related to

SERVER-97217 Multiplanner ranks AND_SORTED plan unfairly

Backlog

related to

SERVER-106829 Plan enumerator generates an AND_SORTED plan with two identical IXSCANs

Backlog

SERVER-108505 indexBasedCE: unable to estimate AND_SORTED nodes with cardinalityEstimate > 0

Closed

SERVER-108694 re-enable index intersection in the plan_stability golden tests

Closed

Assignee:: Maddie Zechar
Reporter:: Steve Tarzia
Participants:: Githook User, Maddie Zechar, Mothra Jira Bot, Steve Tarzia
Votes:: 0 Vote for this issue
Watchers:: 15 Start watching this issue

Created:: Apr 21 2025 02:48:05 PM UTC
Updated:: Aug 26 2025 02:32:26 PM UTC
Resolved:: Aug 26 2025 02:32:26 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates