planner, session: use SessionExtendedInfoSchema if snapshot isn't set (#38794) #38863
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.
This is an automated cherry-pick of #38794
Signed-off-by: wjhuang2016 huangwenjun1997@gmail.com
What problem does this PR solve?
Issue Number: close #38791
Problem Summary:
new
a SessionExtendedInfoSchema in tryLockMDLAndUpdateSchemaIfNecessary(). But it doesn't change the pass-in infoSchema. The compiler/Executor may use the InfoSchema instead of SessionExtendedInfoSchema later.What is changed and how it works?
new
a SessionExtendedInfoSchema in GetDomainInfoSchema(). So that we don't need to new it tryLockMDLAndUpdateSchemaIfNecessary().Check List
Tests
Sysbench with oltp_writeonly workload on a TiDB cluster, and
modify column
many times, no panic occurred.Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.