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

Can't find a proper physical plan for this query #23187

Closed
djshow832 opened this issue Mar 9, 2021 · 1 comment · Fixed by #23238
Closed

Can't find a proper physical plan for this query #23187

djshow832 opened this issue Mar 9, 2021 · 1 comment · Fixed by #23238
Assignees
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@djshow832
Copy link
Contributor

djshow832 commented Mar 9, 2021

Bug Report

The query reports "Can't find a proper physical plan for this query", but it should be executed successfully.

1. Minimal reproduce step (Required)

mysql> create table tbl(n1 varbinary(1024), n2 varbinary(1024), n3 bigint(20), n4 mediumblob, primary key(n1, n2, n3));
Query OK, 0 rows affected (0.00 sec)

mysql> prepare stmt from 'select * from tbl where n1=? and n2>=? and n2<=?';
Query OK, 0 rows affected (0.00 sec)

mysql> set @a='0000', @b='9999';
Query OK, 0 rows affected (0.00 sec)

mysql> execute stmt using @a, @b, @a;
ERROR 1815 (HY000): Internal : Can't find a proper physical plan for this query

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

Returns empty result.

3. What did you see instead (Required)

ERROR 1815 (HY000): Internal : Can't find a proper physical plan for this query

4. What is your TiDB version? (Required)

master.

@ti-srebot
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants