executor: special handling is required when an "auto id out of range" error occurs in insert ignore into ... on on duplicate ... (#39847)

[ti-chi-bot]

This is an automated cherry-pick of #39847

What problem does this PR solve?

Issue Number: close #38950

Problem Summary:

What is changed and how it works?

The code below is added by PR #30301 to fix Issue #29483. When replace encounters a duplicate PRIMARY KEY or UNIQUE KEY, it is expected to have the semantics of DELETE + INSERT, when Auto ID is out of range, the truncated ID is possible to duplicate with an existing ID, this leads to data corruption as unrelated rows are modified and removed.

if err == nil && d.GetInt64() < id {
    // Auto ID is out of range, the truncated ID is possible to duplicate with an existing ID.
    // To prevent updating unrelated rows in the REPLACE statement, it is better to throw an error.
    return autoid.ErrAutoincReadFailed
}

So when the ignore keyword exists in the SQL (or SET sql_mode='NO_ENGINE_SUBSTITUTION';), if the Auto ID is out of range, the above code prevents replace into before it is actually executed, but it also prevents a lot SQLs that need to be executed, so special handling is required when an auto id out of range error occurs in insert ignore into ... on duplicate ... to allow SQL to be executed successfully.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[wuhuizuo]

/hold high priority for trunk branch

[ti-chi-bot]

/unhold

[ti-chi-bot]

@ti-chi-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/unit-test	2f0e78a	link	true	/test unit-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.