Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

executor: set handle changed when col gets auto-updated #44566

Merged
merged 4 commits into from
Jun 11, 2023

Conversation

zyguan
Copy link
Contributor

@zyguan zyguan commented Jun 11, 2023

What problem does this PR solve?

Issue Number: close #44565

Problem Summary: We didn't set handleChanged properly when a on-update-now column gets updated automatically and it's also a pk column, which leads to #44565 .

What is changed and how it works?

Set handleChanged properly in that case.

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

Signed-off-by: zyguan <zhongyangguan@gmail.com>
@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/needs-triage-completed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 needs-cherry-pick-release-5.4 Should cherry pick this PR to release-5.4 branch. needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. and removed do-not-merge/needs-triage-completed labels Jun 11, 2023
Signed-off-by: zyguan <zhongyangguan@gmail.com>
Copy link
Contributor

@cfzjywxk cfzjywxk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

executor/write.go Outdated Show resolved Hide resolved
@ti-chi-bot ti-chi-bot bot added needs-1-more-lgtm Indicates a PR needs 1 more LGTM. approved labels Jun 11, 2023
Signed-off-by: zyguan <zhongyangguan@gmail.com>
executor/write.go Outdated Show resolved Hide resolved
Signed-off-by: zyguan <zhongyangguan@gmail.com>
@ti-chi-bot ti-chi-bot bot added the lgtm label Jun 11, 2023
@ti-chi-bot
Copy link

ti-chi-bot bot commented Jun 11, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, crazycs520

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

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [cfzjywxk,crazycs520]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot removed the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Jun 11, 2023
@ti-chi-bot
Copy link

ti-chi-bot bot commented Jun 11, 2023

[LGTM Timeline notifier]

Timeline:

  • 2023-06-11 05:01:13.647082789 +0000 UTC m=+42223.101844092: ☑️ agreed by cfzjywxk.
  • 2023-06-11 11:09:11.578119494 +0000 UTC m=+64301.032880798: ☑️ agreed by crazycs520.

@ti-chi-bot ti-chi-bot bot merged commit 068933b into pingcap:master Jun 11, 2023
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-6.1: #44568.

ti-chi-bot pushed a commit to ti-chi-bot/tidb that referenced this pull request Jun 11, 2023
Signed-off-by: zyguan <zhongyangguan@gmail.com>
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-6.5: #44569.

ti-chi-bot pushed a commit to ti-chi-bot/tidb that referenced this pull request Jun 11, 2023
Signed-off-by: zyguan <zhongyangguan@gmail.com>
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-7.1: #44570.

ti-chi-bot pushed a commit to ti-chi-bot/tidb that referenced this pull request Jun 11, 2023
Signed-off-by: zyguan <zhongyangguan@gmail.com>
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-5.3: #44571.

ti-chi-bot pushed a commit to ti-chi-bot/tidb that referenced this pull request Jun 11, 2023
Signed-off-by: zyguan <zhongyangguan@gmail.com>
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-5.4: #44572.

ti-chi-bot pushed a commit to ti-chi-bot/tidb that referenced this pull request Jun 11, 2023
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 needs-cherry-pick-release-5.4 Should cherry pick this PR to release-5.4 branch. needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ON UPDATE CURRENT_TIMESTAMP may lead to data inconsistency
4 participants