enable-async-apply-prewrite = true, query result is incorrect with index merge #52901
Labels
affects-8.1
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
severity/critical
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)
cluster-a:
tidb:
config: |
max-index-length = 12287
new_collations_enabled_on_first_bootstrap = true
[experimental]
allow-expression-index = true
tikv:
config: |
[storage]
reserve-space = 0
enable-async-apply-prewrite = true
[pessimistic-txn]
pipelined = true
in-memory = true
cluster-b:
tikv:
config: |
[storage]
reserve-space = "0MB"
tidb:
config: |
max-index-length = 12287
new_collations_enabled_on_first_bootstrap = true
[experimental]
allow-expression-index = true
the default value of "enable-async-apply-prewrite" is false.
2. What did you expect to see? (Required)
the result should be same in two clusters
3. What did you see instead (Required)
in cluster-a:
in cluster-b:
results are same for below sqls:
select /*+ use_index_merge( tbl_43 ) */ * from tbl_43 where not( tbl_43.col_304 between 'YEpfYfPVvhMlHGHSMKm' and 'PE' ) or tbl_43.col_304 in ( 'LUBGzGMA' ) and tbl_43.col_304 between 'HpsjfuSReCwBoh' and 'fta' or not( tbl_43.col_304 between 'MFWmuOsoyDv' and 'TSeMYpDXnFIyp' ) order by col_304 ;
select max( col_304 ) from tbl_43;
select * from tbl_43;
4. What is your TiDB version? (Required)
tidb: e8c397f
tikv: af169fc72dada426c9952200db1d6322ab7990e9
The text was updated successfully, but these errors were encountered: