sql/opt: handle non-unique parent for RBR region inference#171056
Merged
Conversation
When a REGIONAL BY ROW child sets infer_rbr_region_col_using_constraint, the optimizer plans a lookup join into the parent on the FK's non-region columns to infer the region. If those columns aren't a lax key on the parent, the join could return multiple rows per child input row, which tripped an assertion failure in mutation_builder. Allow this configuration: wrap the LeftJoin in an unordered DistinctOn grouped by the child input's key (added via EnsureKey when needed), selecting an arbitrary matching parent row via FirstAgg on the parent's region column. Also moves EnsureKey from decorrelate_funcs.go to general_funcs.go so it can be shared with optbuilder. Fixes cockroachdb#170768 Release note (bug fix): Fixed an internal error that could occur during INSERT/UPDATE/UPSERT on a REGIONAL BY ROW table configured with the infer_rbr_region_col_using_constraint storage parameter when the referenced parent table did not have a unique constraint covering the foreign key's non-region columns. The optimizer now picks an arbitrary matching parent row to infer the region from.
Contributor
|
😎 Merged successfully - details. |
Member
mw5h
approved these changes
May 29, 2026
mw5h
left a comment
Contributor
There was a problem hiding this comment.
@mw5h made 1 comment.
Reviewable status:complete! 1 of 0 LGTMs obtained.
Collaborator
Author
|
TFTR! /trunk merge |
|
Detected infrastructure failure on trunk-merge branch (matched: self-hosted runner lost communication with the server). Automatically resubmitting to merge queue (attempt 1 of 2). (run link) |
|
/trunk merge |
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.
When a REGIONAL BY ROW child sets infer_rbr_region_col_using_constraint, the optimizer plans a lookup join into the parent on the FK's non-region columns to infer the region. If those columns aren't a lax key on the parent, the join could return multiple rows per child input row, which tripped an assertion failure in mutation_builder.
Allow this configuration: wrap the LeftJoin in an unordered DistinctOn grouped by the child input's key (added via EnsureKey when needed), selecting an arbitrary matching parent row via FirstAgg on the parent's region column.
Also moves EnsureKey from decorrelate_funcs.go to general_funcs.go so it can be shared with optbuilder.
Fixes #170768
Release note (bug fix): Fixed an internal error that could occur during INSERT/UPDATE/UPSERT on a REGIONAL BY ROW table configured with the infer_rbr_region_col_using_constraint storage parameter when the referenced parent table did not have a unique constraint covering the foreign key's non-region columns. The optimizer now picks an arbitrary matching parent row to infer the region from.