[BugFix] fix mem leak when caching mv plan context (backport #72300) (backport #72389)#73091
Merged
Merged
Conversation
trueeyu
approved these changes
May 12, 2026
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
2 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.
Why I'm doing:
There are lots of
LakeTabletobject on FOLLOWER after frequently drop&create same materialized view.And objects can't be releazed after fe transfers to LEADER.
What I'm doing:
Removed dropped materialized view object from pending cache and double check materialized view still exists before be added to context cache.
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #72300 done by [Mergify](https://mergify.com).
This is an automatic backport of pull request #72389 done by [Mergify](https://mergify.com).