-
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
sqlbase: avoid decode/encode in Fingerprint #47728
Conversation
I noticed this while taking a look at one of the heap profiles from the tpcc check OOM that @yuzefovich has been fighting: |
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.
Huh, I thought those allocations were expected 🤷♂️
Reviewed 1 of 1 files at r1.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @rohany)
Wow, nice catch! Can you stick a short comment about why we don't call ensure decoded at the top of the method? Maybe this will help the alterpk roachtest! |
Could you add a separate commit here to unskip |
The Fingerprint method introduced in b08d8f4 added an unnecessary decode/encode cycle that didn't exist before, if the input Datum was already in ASCENDING_KEY encoding. This commit restores the original behavior. We should probably backport this to release-20.1. Release note: None
Release note: None
9bff2ca
to
e963949
Compare
TFTRs, both done. bors r+ |
Build succeeded |
We should backport this to 20.1. |
The Fingerprint method introduced in
b08d8f4 added an unnecessary
decode/encode cycle that didn't exist before, if the input Datum was
already in ASCENDING_KEY encoding.
This commit restores the original behavior.
We should probably backport this to release-20.1.
Release note: None