ddl: skip delay for async commit during merging temp index #38138
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 problem does this PR solve?
Issue Number: ref #35983
Problem Summary:
After
@@tidb_ddl_enable_fast_reorg
is enabled, there will be two reorganization steps: backfilll and merge. Because DDL has waited 2.5 seconds in the backfill step, it is guaranteed that none of the async commit transactions with old schema info(the newly adding index's schema state is none) are active. Thus, we don't have to wait another 2.5 seconds in the merge step.What is changed and how it works?
Check List
Tests
Unit test
Integration test
Manual test (add detailed scripts or steps below)
Before this PR, adding index takes 6 seconds even the table is empty:
After this PR, it takes about 3 seconds:
No code
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.