perf-tuning: add column-prune.md (#3246)#3316
Merged
toutdesuite merged 4 commits intoJul 20, 2020
Merged
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
5 tasks
Contributor
Author
|
@toutdesuite please accept the invitation then you can push to the cherry-pick pull requests. |
TomShawn
reviewed
Jul 17, 2020
| - [TiDB Troubleshooting Map](/tidb-troubleshooting-map.md) | ||
| - [Troubleshoot Cluster Setup](/troubleshoot-tidb-cluster.md) | ||
| - [Troubleshoot TiDB Lightning](/troubleshoot-tidb-lightning.md) | ||
| ======= |
Contributor
There was a problem hiding this comment.
@toutdesuite Please resolve the conflict. Be careful about the version difference.
TomShawn
reviewed
Jul 20, 2020
|
|
||
| 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). |
Contributor
There was a problem hiding this comment.
Suggested change
| 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). |
Contributor
There was a problem hiding this comment.
Shall we delete this sentence? Refer to https://github.com/pingcap/docs-cn/blob/release-2.1/column-pruning.md
Contributor
There was a problem hiding this comment.
But users might wonder how to disable this rule.
toutdesuite
reviewed
Jul 20, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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)?