-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
planner: the recursive cte will make UPDATE's result wrong (#49400) #49435
planner: the recursive cte will make UPDATE's result wrong (#49400) #49435
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-6.5 #49435 +/- ##
================================================
Coverage ? 73.7668%
================================================
Files ? 1088
Lines ? 350442
Branches ? 0
================================================
Hits ? 258510
Misses ? 75424
Partials ? 16508 |
/retest |
2 similar comments
/retest |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hawkingrei, winoros The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
This is an automated cherry-pick of #49400
What problem does this PR solve?
Issue Number: close #48969
Problem Summary:
What changed and how does it work?
When we build the recursive CTE, we'll first try to build it as a non-recursive one. And going to treat it as a real recursive one when we actually meet the recursive part.
So the non-recursive part is built twice, but we don't pop the rowid information correctly, causing the UPDATE's result wrong.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.