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

Unexpected results caused by column pruning rules #11905

Closed
bb7133 opened this issue Aug 28, 2019 · 0 comments · Fixed by #11927
Closed

Unexpected results caused by column pruning rules #11905

bb7133 opened this issue Aug 28, 2019 · 0 comments · Fixed by #11927
Assignees
Labels
type/bug The issue is confirmed as a bug.

Comments

@bb7133
Copy link
Member

bb7133 commented Aug 28, 2019

Bug Report

  1. What did you do?
    Run SQLs like the following:
mysql> select 1 from (select sleep(1)) t;
  1. What did you expect to see?
mysql> select 1 from (select sleep(1)) t;
+---+
| 1 |
+---+
| 1 |
+---+
1 row in set (1.00 sec)
  1. What did you see instead?
mysql> select 1 from (select sleep(1)) t;
+---+
| 1 |
+---+
| 1 |
+---+
1 row in set (0.00 sec)

Notice the execution time, sleep(1) is not executed.

  1. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?
sh> tidb-server -V
Release Version: v4.0.0-alpha-142-g932c4a7bf-dirty
Git Commit Hash: 932c4a7bfc3ad448a2d4c8d68acbb0264d9a588a
Git Branch: master
UTC Build Time: 2019-08-28 06:20:44
GoVersion: go version go1.12 linux/amd64
Race Enabled: false
TiKV Min Version: v3.0.0-60965b00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants