Internal : Can't find a proper physical plan for this query

[aytrack]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

CREATE TABLE IDT_9903 (COL1 LONGBLOB,COL2 SMALLINT(4),COL3 DATETIME(2),KEY U_M_COL(COL1(10),COL2,COL3));
prepare stmt from 'select t1.col1, t2.col2 from IDT_9903 as t1 inner join IDT_9903 as t2 on t1.col1 = t2.col1 where t1.col1 = ?;';
execute stmt using@a;

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

mysql root@127.0.0.1:test>  CREATE TABLE IDT_9903 (COL1 LONGBLOB,COL2 SMALLINT(4),COL3 DATETIME(2),KEY U_M_COL(COL1(10),COL2,COL3));
Query OK, 0 rows affected
Time: 0.006s
mysql root@127.0.0.1:test> prepare stmt from 'select t1.col1, t2.col2 from IDT_9903 as t1 inner join IDT_9903 as t2 on t1.col1 = t2.col1 where t1.col1 = ?;';
Query OK, 0 rows affected
Time: 0.001s
mysql root@127.0.0.1:test> set @a=NULL;
Query OK, 0 rows affected
Time: 0.001s
mysql root@127.0.0.1:test> execute stmt using@a;
+------+------+
| col1 | col2 |
+------+------+

3. What did you see instead (Required)

mysql root@127.0.0.1:test>  CREATE TABLE IDT_9903 (COL1 LONGBLOB,COL2 SMALLINT(4),COL3 DATETIME(2),KEY U_M_COL(COL1(10),COL2,COL3));
Query OK, 0 rows affected
Time: 0.006s
mysql root@127.0.0.1:test> prepare stmt from 'select t1.col1, t2.col2 from IDT_9903 as t1 inner join IDT_9903 as t2 on t1.col1 = t2.col1 where t1.col1 = ?;';
Query OK, 0 rows affected
Time: 0.001s
mysql root@127.0.0.1:test> set @a=NULL;
Query OK, 0 rows affected
Time: 0.001s
mysql root@127.0.0.1:test> execute stmt using@a;
(1815, "Internal : Can't find a proper physical plan for this query")

4. What is your TiDB version? (Required)

master 550ca8e
5.0-rc f41ca49

[eurekaka]

Fixed by #23238.

[ti-srebot]

Please edit this comment or add a new comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions