infoschema: fix the value of MaxColumnID
in memDB (#45764)
#45817
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 #45764
What problem does this PR solve?
Issue Number: close #45744
Problem Summary:
At present, it is the
MaxColumnID
of the table in theinformation_schema
database, which affectsmodify column
,add column
(this action has no problem in behavior, but can cause problems with column ids that are not unique).
The table under
metrics_schema
has a similar problem, and the table underperformance_schema
does not.What is changed and how it works?
MaxColumnID
in theinformation_schema
andmetrics_schema
databases.MaxIndexD
, although this field is not currently used.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.