Skip to content

optimizer tracer seem it collected and dropped some logical optimized step #40662

@AilinKid

Description

@AilinKid

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

image

SQL:

 trace plan SELECT type, created_at, actor_login, action, number, repo_name FROM github_events WHERE LOWER(actor_login) = LOWER('NGAUT') ORDER BY created_at DESC LIMIT 1;

There is indeed a column-substitute from LOWER(actor_login) to _V$_index_ge_on_actor_login_lower_0 in logical rule &gcSubstituter{}

But we can't tell it from the dumped tracer file

FRq9cBFqf9

optimizer_trace_57IjVj4HkZhA4aGPR6SOSQ==_1673853774961365102.zip

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

Better add it

3. What did you see instead (Required)

Miss it

4. What is your TiDB version? (Required)

ossinsight special-v6.5.0

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions