release-21.1: opt: do not provide project ordering for columns removed when simplified #64481
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.
Backport 1/1 commits from #64444.
/cc @cockroachdb/release
Previously,
projectCanProvideOrdering
did not simplify an orderingbase on an FD set if the original ordering could be provided, while
projectBuildChildReqOrdering
always attempted to simplify an ordering.In #64342 the behavior of
OrderingChoice.Simplify
changed to removecolumns in groups that are not known to be equivalent by the FD. As a
result,
projectCanProvideOrdering
could return true in cases where thesimplified ordering, with some columns removed, could not be provided,
causing
ordering.projectBuildChildReqOrdering
to panic.This commit updates
ordering.projectCanProvideOrdering
so that theordering is always simplified, matching the behavior of
ordering.projectBuildChildReqOrdering
.Fixes #64399
Release note: None