session: add some compatibility checks for non-transactional DML#34127
session: add some compatibility checks for non-transactional DML#34127ti-chi-bot merged 10 commits intopingcap:masterfrom
Conversation
|
[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 submitting an approval review. |
9f14213 to
008bd7a
Compare
|
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/19f7b391305fc753d5a62d44b7cdd63a894a4b64 |
|
Would there be some other session variables which should be skipped too? |
Maybe I didn't find other session variables that should be ignored. But there are some that I think are worth consideration:
|
Signed-off-by: ekexium <ekexium@gmail.com>
Signed-off-by: ekexium <ekexium@gmail.com>
Signed-off-by: ekexium <ekexium@gmail.com>
Signed-off-by: ekexium <ekexium@gmail.com>
Signed-off-by: ekexium <ekexium@gmail.com>
8ae652b to
f3cf670
Compare
Signed-off-by: ekexium <ekexium@gmail.com>
Signed-off-by: ekexium <ekexium@gmail.com>
Signed-off-by: ekexium <ekexium@gmail.com>
|
/run-unit-test |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 6f052af |
TiDB MergeCI notify
|
Signed-off-by: ekexium ekexium@gmail.com
What problem does this PR solve?
Issue Number: ref #33485
Problem Summary:
A Non-transactional DML is not a SELECT.
sql_select_limitcan limit the select query that is used to generate shard jobs and can lead to unexpected results for a "DML". So it should be ignored when executing the query.What is changed and how it works?
sql_select_limitandtidb_read_staleness.tidb_snapshot, batch-dml, or weak read consistency is used.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.