test: add EXPLAIN ANALYZE alias regression - #24501
Merged
mergify[bot] merged 5 commits intoMay 21, 2026
Merged
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
heni02
approved these changes
May 21, 2026
Contributor
Merge Queue Status
This pull request spent 46 minutes 45 seconds in the queue, with no time running CI. Waiting for
All conditions
ReasonThe merge conditions cannot be satisfied due to failing checks HintYou may have to fix your CI before adding the pull request to the queue again. |
Contributor
Merge Queue Status
This pull request spent 2 hours 31 minutes 49 seconds in the queue, including 1 hour 3 minutes 29 seconds running CI. Required conditions to merge
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What type of PR is this?
Which issue(s) this PR fixes:
issue #23121
What this PR does / why we need it:
The
EXPLAIN ANALYZEalias-resolution failure described in #23121 could not be reproduced on currentupstream/mainwith the issue's grouped left-join shape. The query resolvesc.full_namecorrectly and returns an analyzed plan.This PR adds a focused BVT regression case to keep that behavior covered without changing planner or binder logic.
Changes:
EXPLAIN ANALYZEregression scenario for grouped joins that reference table-alias columns in the select list and group key.column 'c.full_name' does not existfailure is absent.Validation:
make buildEXPLAIN ANALYZEsucceeded and emittedGroup Key: c.id, c.full_name.