sql: remove vectorize_row_count_threshold setting #62164
Merged
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.
This commit removes
vectorize_row_count_threshold
session variable andthe corresponding cluster setting. In 21.1 release these are set to 0 by
default, and in 21.2 release that default behavior cannot be changed.
This marks another step towards the start of deprecating the row-by-row
execution engine.
Fixes: #53893.
Release note (sql change):
sql.defaults.vectorize_row_count_threshold
cluster setting as well as corresponding
vectorize_row_count_threshold
session variable have been removed. From now on, CockroachDB will behave
exactly as if these were set to 0 (last default value).