Planner will not consider IndexMerge when an alternative (non selective) index exists #26764
Labels
affects-5.4
This bug affects 5.4.x versions.
affects-6.1
affects-6.5
sig/planner
SIG: Planner
type/enhancement
The issue or PR belongs to an enhancement.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
I expect more or less the same query plan from both queries.
The column
id
is a unique index. It seems that because an index is considered forid != 107053556
(but not useful), IndexMerge is not considered at all.3. What did you see instead (Required)
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: