-
Notifications
You must be signed in to change notification settings - Fork 709
perf-tuning: add column-prune.md (#3246) #3316
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
perf-tuning: add column-prune.md (#3246) #3316
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
@toutdesuite please accept the invitation then you can push to the cherry-pick pull requests. |
TOC.md
Outdated
| - [TiDB Troubleshooting Map](/tidb-troubleshooting-map.md) | ||
| - [Troubleshoot Cluster Setup](/troubleshoot-tidb-cluster.md) | ||
| - [Troubleshoot TiDB Lightning](/troubleshoot-tidb-lightning.md) | ||
| ======= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@toutdesuite Please resolve the conflict. Be careful about the version difference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TomShawn Resolved. PTAL~
TomShawn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
column-pruning.md
Outdated
|
|
||
| In this query, only column a and column b are used, and column c and column d are redundant. Regarding the query plan of this statement, the `Selection` operator uses column b. Then the `DataSource` operator uses columns a and column b. Columns c and column d can be pruned because the `DataSource` operator does not read them. | ||
|
|
||
| Therefore, when TiDB performs a top-down scanning during the logic optimization phase, redundant columns are pruned to reduce waste of resources. This scanning process is called "Column Pruning", corresponding to the `columnPruner` rule. If you want to disable this rule, refer to [The Blocklist of Optimization Rules and Expression Pushdown](/blocklist-control-plan.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Therefore, when TiDB performs a top-down scanning during the logic optimization phase, redundant columns are pruned to reduce waste of resources. This scanning process is called "Column Pruning", corresponding to the `columnPruner` rule. If you want to disable this rule, refer to [The Blocklist of Optimization Rules and Expression Pushdown](/blocklist-control-plan.md). | |
| Therefore, when TiDB performs a top-down scanning during the logic optimization phase, redundant columns are pruned to reduce waste of resources. This scanning process is called "Column Pruning", corresponding to the `columnPruner` rule. If you want to disable this rule, refer to [The Blocklist of Optimization Rules and Expression Pushdown](https://docs.pingcap.com/tidb/dev/blocklist-control-plan). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@toutdesuite PTAL
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we delete this sentence? Refer to https://github.com/pingcap/docs-cn/blob/release-2.1/column-pruning.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But users might wonder how to disable this rule.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated~
cherry-pick #3246 to release-2.1
What is changed, added or deleted? (Required)
add column-prune.md
Merge #3043 to fix CI failure
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?