Fix DBUG_PRINT format of group_trp->records
#3537
Open
Conversation
This file contains 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
3 tasks
LinuxJedi
approved these changes
Sep 30, 2024
LinuxJedi
force-pushed
the
11.2-my_snprintf
branch
from
115aec0
to
42976ba
Compare
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.
The Jira issue number for this PR is: MDEV-21978This commit backports a lone fix from #3360 for 11.2, our oldest 11.x in maintenance.
It is the only mistake introduced during 11.0–11.2.
Release Notes
Not needed
How can this PR be tested?
Use
DBUGto confirm that the log doesn’t have an extraneousllsuffixBasing the PR against the correct MariaDB version
This is a new feature or a refactoring, and the PR is based against themainbranch.PR quality check