-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opt: compute join output col map properly #39052
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @RaduBerinde)
bors r+ |
Build failed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 2 files at r1.
Reviewable status: complete! 2 of 0 LGTMs obtained
Fixes cockroachdb#39010. This manifested with the advent of WITH, but the problem was actually that we were computing a join output map somewhat incorrectly. This never actually caused problems before because we would prune any columns that could cause there to be a disparity between the two ways of computing the size of the ColMap, but since WITH doesn't support pruning, it caused issues. I also replaced some other uses of Len that were potentially sketchy. Release note: None
Shoudl we re-bors this? |
oops, yup, meant to. bors r+ |
39052: opt: compute join output col map properly r=justinj a=justinj Fixes #39010. This manifested with the advent of WITH, but the problem was actually that we were computing a join output map somewhat incorrectly. This never actually caused problems before because we would prune any columns that could cause there to be a disparity between the two ways of computing the size of the ColMap, but since WITH doesn't support pruning, it caused issues. I also replaced some other uses of Len that were potentially sketchy. Release note: None Co-authored-by: Justin Jaffray <justin@cockroachlabs.com>
Build succeeded |
Fixes #39010.
This manifested with the advent of WITH, but the problem was actually
that we were computing a join output map somewhat incorrectly. This
never actually caused problems before because we would prune any columns
that could cause there to be a disparity between the two ways of
computing the size of the ColMap, but since WITH doesn't support
pruning, it caused issues.
I also replaced some other uses of Len that were potentially sketchy.
Release note: None