Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.1.0-rc0, 9.1.0-rc1025
Affects Version/s: None
Component/s: None
Labels:
- M2

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Linked BF Score:
200
CAR Domain/s:
None

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

For transitive multi-table joins, INLJ enumeration costs only edges[0]. Edge order follows query syntax, so equivalent queries may use different selectivity estimates and choose different plans/costs.

related to

SERVER-132577 INLJ cost model and execution disagree on which join predicate drives the index probe

Closed

SERVER-131574 Disable test case in join_costing_invariants.js

Closed

SERVER-137841 Complete TODO listed in SERVER-131547

Needs Scheduling

SERVER-116534 Consider multiple edges when picking the index for an INLJ

Open

Assignee:: Alya Berciu
Reporter:: Max Verbinnen
Participants:: Alya Berciu, Max Verbinnen
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Jul 16 2026 12:27:10 PM UTC
Updated:: Oct 24 2026 04:31:42 AM UTC
Resolved:: Oct 22 2026 12:41:05 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty