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

TiDB auto increment MySQL-compatible behavior clarification (#19861) #19965

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #19861

What is changed, added or deleted? (Required)

Improved the MySQL compatibility mode section in auto-increment.md by:

  1. Providing a clearer introduction that immediately states the purpose and benefits
  2. Adding practical examples showing behavior differences between AUTO_ID_CACHE 1 and default mode
  3. Explaining when and why gaps might occur in the sequence
  4. Restructuring the version-specific notes for better readability
  5. Adding information about v8.1.0 changes regarding forceRebase operation

These changes make it easier for users to:

  • Understand the practical differences between MySQL compatibility mode and default mode
  • See concrete examples of ID allocation behavior in different scenarios
  • Understand the performance implications across different TiDB versions

Which TiDB version(s) do your changes apply to? (Required)

Since this change includes information about behavior changes across multiple versions (v6.4.0 and v8.1.0) and documents current functionality, it should be applied to:

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.4 (TiDB 8.4 versions)
  • v8.3 (TiDB 8.3 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot ti-chi-bot added lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. type/enhancement The issue or PR belongs to an enhancement. labels Mar 3, 2025
@lilin90
Copy link
Member

lilin90 commented Mar 4, 2025

/approve

Copy link

ti-chi-bot bot commented Mar 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lilin90

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:

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 added the approved label Mar 4, 2025
@ti-chi-bot ti-chi-bot bot merged commit 30a3f4f into pingcap:release-8.5 Mar 4, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants