inconsistent SQL bind caches after recreating bind with different bind_sql for a same original_sql #25842
Labels
affects-4.0
This bug affects 4.0.x versions.
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
epic/sql-plan-management
severity/major
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Start 2 tidb-servers, execute create / drop binding statements on tidb-1, and observe the results of
show global bindings
on tidb-2.This is the output on tidb-1, which is as expected.
This is the output on tidb-2:
We can see that, tidb-2 has an invalid cached bind for
use index(a)
hint.2. What did you expect to see? (Required)
tidb-1 and tidb-2 have same cached bindings.
3. What did you see instead (Required)
tidb-2 has one more cached binding than tidb-1, which is expected to be removed.
4. What is your TiDB version? (Required)
4.0.12, master
The text was updated successfully, but these errors were encountered: