Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Optimization
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

Open

SERVER-131574 Disable test case in join_costing_invariants.js

Closed

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

Open

Assignee:: Unassigned
Reporter:: Max Verbinnen
Participants:: Max Verbinnen
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jul 16 2026 12:27:10 PM UTC
Updated:: Aug 31 2026 04:38:54 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty