*: remove SchemaVersion in TransactionContext#24236
*: remove SchemaVersion in TransactionContext#24236ti-chi-bot merged 2 commits intopingcap:masterfrom
Conversation
|
/lgtm |
|
/lgtm |
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by writing |
|
Please resolve the conflicts @xhebox . |
Signed-off-by: xhe <xw897002528@gmail.com>
|
/unhold |
|
Have merged the previous PR, continue to merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: a393b3e |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
cherry pick to release-4.0 in PR #24536 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
cherry pick to release-5.0 in PR #24537 |
What problem does this PR solve?
The main issue: #24233
Problem Summary: Follow #24230, the bug is that when
set @@tidb_snapshot="xxxx",SchemaVersionis not updated to the old schema version.Since the update of
SchemaVersionandInfoSchemais messy(there are multiple setters forInfoschema,SchemaVersionandSnapshotInfoschema), I removedSchemaVersioncompletely and rely on the previousGetInfoSchema(which will get snapshot if there is one, then the current schema) to retrieve schema version.Check List
Tests
Release note