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

SPM: the regression issue of capturing baseline failure #22203

Closed
ChenPeng2013 opened this issue Jan 6, 2021 · 2 comments · Fixed by #22219
Closed

SPM: the regression issue of capturing baseline failure #22203

ChenPeng2013 opened this issue Jan 6, 2021 · 2 comments · Fixed by #22219
Labels

Comments

@ChenPeng2013
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

use test;
drop table if exists t;
create table t(a int);
select * from t;
select * from t;
admin capture bindings;
show global bindings;

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

mysql> show global bindings;
+-----------------+---------------------------------------------------------+------------+--------+-------------------------+-------------------------+---------+-----------+---------+
| Original_sql    | Bind_sql                                                | Default_db | Status | Create_time             | Update_time             | Charset | Collation | Source  |
+-----------------+---------------------------------------------------------+------------+--------+-------------------------+-------------------------+---------+-----------+---------+
| select * from t | SELECT /*+ use_index(@`sel_1` `test`.`t` )*/ * FROM `t` | test       | using  | 2021-01-06 06:14:15.725 | 2021-01-06 06:14:15.725 |         |           | capture |
+-----------------+---------------------------------------------------------+------------+--------+-------------------------+-------------------------+---------+-----------+---------+
1 row in set (0.00 sec)

3. What did you see instead (Required)

mysql> show global bindings;
Empty set (0.00 sec)

4. What is your TiDB version? (Required)

master: v4.0.0-beta.2-1970-g238670269
release-4.0: v4.0.9-24-ge082513b2

@ChenPeng2013 ChenPeng2013 added type/bug The issue is confirmed as a bug. epic/sql-plan-management labels Jan 6, 2021
@eurekaka
Copy link
Contributor

eurekaka commented Jan 6, 2021

log level must be set debug to reproduce this problem.

@ti-srebot
Copy link
Contributor

ti-srebot commented Jan 8, 2021

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

unreleased

6. Fixed versions

master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants