copy: fix vectorized copy for INT2 and INT4 #102298
Merged
+54
−13
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 fixes a recently introduced bug where we forgot to implement the special behavior in the vec handler for INT2 and INT4 types which would then could lead to a runtime crash if such a type is used in the schema. Int types are special because the vectorized engine handles them precisely (i.e. it uses int16, int32, and int64 accordingly) whereas the row engine always internally defaults to int64.
Fixes: #102181.
Release note (bug fix): In alpha and beta 23.1.0 releases CockroachDB could crash when evaluating COPY command in some cases when the schema had INT2 and / or INT4 type, and this is now fixed.