Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Oct 29, 2025

Why I'm doing:

This is a follow up pr of #63724.

What I'm doing:

test as below:

before(2-stage agg):

$ mysqlslap --concurrency=1     --iterations=3     --query="/home/ubuntu/lism/q9.sql"     --delimiter=";" -h 127.0.0.1  -P 9130 -u root  --create-schema=hits
Benchmark
        Average number of seconds to run all queries: 0.308 seconds
        Minimum number of seconds to run all queries: 0.304 seconds
        Maximum number of seconds to run all queries: 0.311 seconds
        Number of clients running queries: 1
        Average number of queries per client: 2

after(4-stage agg with #63660):

$ mysqlslap --concurrency=1     --iterations=3     --query="/home/ubuntu/lism/q9.sql"     --delimiter=";" -h 127.0.0.1  -P 9130 -u root  --create-schema=hits
Benchmark
        Average number of seconds to run all queries: 0.202 seconds
        Minimum number of seconds to run all queries: 0.191 seconds
        Maximum number of seconds to run all queries: 0.219 seconds
        Number of clients running queries: 1
        Average number of queries per client: 1

Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 4.0
    • 3.5
    • 3.4
    • 3.3

This is an automatic backport of pull request #64668 done by [Mergify](https://mergify.com).

…le node env when group by column is skew (#64668)

Signed-off-by: shuming.li <[email protected]>
(cherry picked from commit 0cc1a5f)
@mergify
Copy link
Contributor Author

mergify bot commented Oct 29, 2025

🧪 CI Insights

Here's what we observed from your CI run for f72bc28.

🟢 All jobs passed!

But CI Insights is watching 👀

@wanpengfei-git wanpengfei-git merged commit 3c26a9d into branch-4.0 Oct 29, 2025
44 of 45 checks passed
@wanpengfei-git wanpengfei-git deleted the mergify/bp/branch-4.0/pr-64668 branch October 29, 2025 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants