Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Point get plan got error: runtime error: index out of range [-1] #58581

Closed
joechenrh opened this issue Dec 27, 2024 · 2 comments · Fixed by #58687
Closed

Point get plan got error: runtime error: index out of range [-1] #58581

joechenrh opened this issue Dec 27, 2024 · 2 comments · Fixed by #58687
Assignees
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. impact/panic severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@joechenrh
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create table t (id int unique key, c int);
insert into t values (1, 10);
insert into t values (2, 20);
insert into t values (3, 30);
select _tidb_rowid from t where id in (1, 2, 3);

2. What did you expect to see? (Required)

+-------------+                                                                             
| _tidb_rowid |                                                                             
+-------------+                                                                             
|           1 |                                                                             
|           2 |                                                                             
|           3 |                                                                             
+-------------+   

3. What did you see instead (Required)

ERROR 1105 (HY000): runtime error: index out of range [-1]

4. What is your TiDB version? (Required)

@joechenrh joechenrh added the type/bug The issue is confirmed as a bug. label Dec 27, 2024
@joechenrh
Copy link
Contributor Author

Maybe introduced by #18516

@Defined2014
Copy link
Contributor

Defined2014 commented Dec 27, 2024

It is related to fastPlan + batchPointGet + _tidb_rowid, we can use the following sql to skip it

set tidb_opt_fix_control = "52592:ON";

@hawkingrei hawkingrei added the sig/planner SIG: Planner label Dec 27, 2024
@hawkingrei hawkingrei assigned hawkingrei and unassigned hawkingrei Jan 2, 2025
@hawkingrei hawkingrei added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Jan 2, 2025
@Defined2014 Defined2014 added affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. and removed 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 may-affects-8.1 may-affects-8.5 labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. impact/panic severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
5 participants