Skip to content
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

colbuilder: don't use optimized IN operator for empty tuple #88195

Merged
merged 1 commit into from
Sep 20, 2022

Conversation

yuzefovich
Copy link
Member

@yuzefovich yuzefovich commented Sep 19, 2022

This commit makes it so that we don't use the optimized IN operator for empty tuples since they handle NULLs incorrectly. This wasn't supposed to happen already due to 9b590d3 but there we only looked at the type and not at the actual datum. This is not a production bug since the optimizer normalizes such expressions away.

Fixes: #88141.

Epic: CRDB-20535

Release note: None

This commit makes it so that we don't use the optimized IN operator for
empty tuples since they handle NULLs incorrectly. This wasn't supposed
to happen already due to 9b590d3 but
there we only looked at the type and not at the actual datum. This is
not a production bug since the optimizer normalizes such expressions
away.

Release note: None
@yuzefovich yuzefovich requested review from mgartner and a team September 19, 2022 23:14
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Collaborator

@DrewKimball DrewKimball left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @mgartner)

@yuzefovich
Copy link
Member Author

TFTR!

bors r+

@craig
Copy link
Contributor

craig bot commented Sep 20, 2022

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Sep 20, 2022

Build succeeded:

@craig craig bot merged commit f363dba into cockroachdb:master Sep 20, 2022
@blathers-crl
Copy link

blathers-crl bot commented Sep 20, 2022

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from 8da0320 to blathers/backport-release-22.2-88195: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 22.2.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

@mgartner
Copy link
Collaborator

Thanks for the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

sql: vectorized engine incorrectly evaluates NOT (x IN ())
4 participants