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

topsql failed catch the running SQL when Top SQL is enabled in execution #33859

Closed
crazycs520 opened this issue Apr 11, 2022 · 0 comments · Fixed by #33861
Closed

topsql failed catch the running SQL when Top SQL is enabled in execution #33859

crazycs520 opened this issue Apr 11, 2022 · 0 comments · Fixed by #33861
Assignees
Labels
severity/minor sig/diagnosis SIG: Diagnosis type/bug The issue is confirmed as a bug.

Comments

@crazycs520
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. Create table t1 and insert into 10000000 rows data.
  2. Execute following SQLs in client-A and client-B at same time:
select count(*),sum(a+b),sum(b+d),sum(c+d*2), sum(d*2+a*b), avg(a*b*d), avg(b*c), avg(c*d),avg(a*b*d), avg(2*b*c), avg(3*c*d), sum(a*b*c), sum(b*d) from t1;
select count(*) from t1 as t0 join t1 as t1 on t0.a != t1.a;
  1. enable TopSQL during the upper SQL execution:
set @@global.tidb_enable_top_sql=1;

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

TopSQL should catch the running SQL when Top SQL is enabled in execution.

3. What did you see instead (Required)

topsql failed catch the running SQL when Top SQL is enabled in execution.

4. What is your TiDB version? (Required)

0d7602eb6551c9a53732be4da37d6ac2f22e375d (HEAD -> master, origin/master)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/minor sig/diagnosis SIG: Diagnosis type/bug The issue is confirmed as a bug.
Projects
None yet
1 participant