-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The test case below generates the following plan where the two inputs to the `AND_SORTED` are identical. The other two plans for this pipeline are affected by SERVER-89110
inputStage: {
stage: 'AND_SORTED',
costEstimate: 0.00011999999999999999,
cardinalityEstimate: 0,
estimatesMetadata: { ceSource: 'Code' },
inputStages: [
{
stage: 'IXSCAN',
costEstimate: 0.000009999999999999999,
cardinalityEstimate: 0,
numKeysEstimate: 0,
estimatesMetadata: { ceSource: 'Sampling' },
keyPattern: { b: 1 },
indexName: 'b_1',
isMultiKey: true,
multiKeyPaths: { b: [ 'b' ] },
isUnique: false,
isSparse: false,
isPartial: false,
indexVersion: 2,
direction: 'forward',
indexBounds: { b: [ '[13, 13]' ] }
},
{
stage: 'IXSCAN',
costEstimate: 0.000009999999999999999,
cardinalityEstimate: 0,
numKeysEstimate: 0,
estimatesMetadata: { ceSource: 'Sampling' },
keyPattern: { b: 1 },
indexName: 'b_1',
isMultiKey: true,
multiKeyPaths: { b: [ 'b' ] },
isUnique: false,
isSparse: false,
isPartial: false,
indexVersion: 2,
direction: 'forward',
indexBounds: { b: [ '[13, 13]' ] }
}
]
}
- is related to
-
SERVER-104102 Disable AND_SORTED index intersection plans in plan enumeration
-
- Closed
-
-
SERVER-107917 Estimate for AND_SORTED applies exponential backoff even if ranges belong to the same index
-
- Needs Scheduling
-
- related to
-
SERVER-89110 Plan enumerator can generate duplicate plans
-
- Backlog
-
-
SERVER-107917 Estimate for AND_SORTED applies exponential backoff even if ranges belong to the same index
-
- Needs Scheduling
-