Update MySQL version references (#22839)

dveeden · web-flow · commit fadf513cc39f · 2026-05-09T05:05:35.000Z
diff --git a/.gemini/styleguide.md b/.gemini/styleguide.md
@@ -46,7 +46,11 @@ You are acting as a **senior technical writer** who is reviewing TiDB documentat
 
 - Inconsistent use of technical terms
 
-    _"TiDB Cloud Serverless clusters" vs. "TiDB Serverless clusters"_ – pick one.
+    _"TiDB Cloud Starter instances" vs. "TiDB Starter instances"_ – pick one.
+
+- Incorrect MySQL version notation
+
+    Use `MySQL 8.0`, `MySQL 8.4`, or `MySQL 8.x`. Do not use `MySQL v8.0`. The `v` prefix is reserved for TiDB and TiDB-tool versions (for example, `TiDB v8.5` and `DM v2.0`). _"MySQL v8.0"_ → _"MySQL 8.0"_.
 
 - Unclear step instructions
 
diff --git a/_docHome.md b/_docHome.md
@@ -82,7 +82,7 @@ Connect your application with the languages and frameworks you prefer.
 
 <DocHomeCard href="/tidb/stable/mysql-compatibility" label="MySQL Compatibility" icon="oss-mysql-blue">
 
-TiDB is highly compatible with the MySQL protocol and the common features and syntax of MySQL 5.7 and MySQL 8.0.
+TiDB is highly compatible with the MySQL protocol and the common features and syntax of MySQL 8.x.
 
 </DocHomeCard>
 
diff --git a/character-set-and-collation.md b/character-set-and-collation.md
@@ -443,7 +443,7 @@ String > Column > Table > Database > Server
 
 ## Validity check of characters
 
-If the specified character set is `utf8` or `utf8mb4`, TiDB only supports the valid `utf8` characters. For invalid characters, TiDB reports the `incorrect utf8 value` error. This validity check of characters in TiDB is compatible with MySQL 8.0 but incompatible with MySQL 5.7 or earlier versions.
+If the specified character set is `utf8` or `utf8mb4`, TiDB only supports the valid `utf8` characters. For invalid characters, TiDB reports the `incorrect utf8 value` error. This validity check of characters in TiDB is compatible with MySQL 8.x but incompatible with MySQL 5.7 or earlier versions.
 
 To disable this error reporting, use `set @@tidb_skip_utf8_check=1;` to skip the character check.
 
diff --git a/develop/dev-guide-mysql-tools.md b/develop/dev-guide-mysql-tools.md
@@ -27,21 +27,21 @@ After the installation, you can connect to TiDB using the following command:
 mysql --host <tidb_server_host> --port 4000 -u root -p --comments
 ```
 
-The MySQL v9.0 client on macOS cannot correctly load the `mysql_native_password` plugin, causing the error `ERROR 2059 (HY000): Authentication plugin 'mysql_native_password' cannot be loaded` when connecting to TiDB. To address this issue, it is recommended to install and use the MySQL v8.0 client to connect to TiDB. Run the following commands to install it:
+The MySQL 9.x client on macOS cannot correctly load the `mysql_native_password` plugin, causing the error `ERROR 2059 (HY000): Authentication plugin 'mysql_native_password' cannot be loaded` when connecting to TiDB. To address this issue, it is recommended to install and use the MySQL 8.0 client to connect to TiDB. Run the following commands to install it:
 
 ```shell
 brew install mysql-client@8.0
 brew unlink mysql
 brew link mysql-client@8.0
 ```
 
-If you still encounter errors, you can specify the installation path of the MySQL v8.0 client to connect to TiDB. Run the following command:
+If you still encounter errors, you can specify the installation path of the MySQL 8.0 client to connect to TiDB. Run the following command:
 
 ```shell
 /opt/homebrew/opt/mysql-client@8.0/bin/mysql --comments --host ${YOUR_IP_ADDRESS} --port ${YOUR_PORT_NUMBER} -u ${your_user_name} -p
 ```
 
-Replace `/opt/homebrew/opt/mysql-client@8.0/bin/mysql` in the preceding command with the installation path of the MySQL v8.0 client in your actual environment.
+Replace `/opt/homebrew/opt/mysql-client@8.0/bin/mysql` in the preceding command with the installation path of the MySQL 8.0 client in your actual environment.
 
 </div>
 
diff --git a/dm/dm-overview.md b/dm/dm-overview.md
@@ -16,7 +16,7 @@ aliases: ['/docs/tidb-data-migration/dev/overview/','/docs/tidb-data-migration/d
 
 ## Basic features
 
-- **Compatibility with MySQL.** DM is compatible with the MySQL protocol and most of the features and syntax of MySQL 5.7 and MySQL 8.0.
+- **Compatibility with MySQL.** DM is compatible with the MySQL protocol and most of the features and syntax of MySQL 5.7 and MySQL 8.x.
 - **Replicating DML and DDL events.** It supports parsing and replicating DML and DDL events in MySQL binlog.
 - **Migrating and merging MySQL shards.** DM supports migrating and merging multiple MySQL database instances upstream to one TiDB database downstream. It supports customizing replication rules for different migration scenarios. It can automatically detect and handle DDL changes of upstream MySQL shards, which greatly reduces the operational cost.
 - **Various types of filters.** You can predefine event types, regular expressions, and SQL expressions to filter out MySQL binlog events during the data migration process.
@@ -41,7 +41,7 @@ Before using the DM tool, note the following restrictions:
 
 + Database version requirements
 
-    - MySQL version 5.6 ~ 8.0
+    - MySQL version 5.6 ~ 8.4
     - MariaDB version >= 10.1.2 (experimental features)
 
     > **Note:**
diff --git a/dm/dm-precheck.md b/dm/dm-precheck.md
@@ -47,8 +47,7 @@ Regardless of the migration mode you choose, the precheck always includes the fo
 
     > **Warning:**
     >
-    > - Migrating data from MySQL 8.0 to TiDB using DM is an experimental feature (introduced since DM v2.0). It is NOT recommended that you use it in a production environment.
-    > - Migrating data from MariaDB to TiDB using DM is an experimental feature. It is NOT recommended that you use it in a production environment.
+    > Migrating data from MariaDB to TiDB using DM is an experimental feature. It is NOT recommended that you use it in a production environment.
 
 - Compatibility of the upstream MySQL table schema
 
diff --git a/faq/tidb-faq.md b/faq/tidb-faq.md
@@ -44,7 +44,7 @@ Yes, it is. When all the required services are started, you can use TiDB as easi
 
 ### How is TiDB compatible with MySQL?
 
-Currently, TiDB supports the majority of MySQL 8.0 syntax, but does not support triggers, stored procedures, and user-defined functions. For more details, see [Compatibility with MySQL](/mysql-compatibility.md).
+Currently, TiDB supports the majority of MySQL 8.x syntax, but does not support triggers, stored procedures, and user-defined functions. For more details, see [Compatibility with MySQL](/mysql-compatibility.md).
 
 ### Does TiDB support distributed transactions?
 
diff --git a/functions-and-operators/aggregate-group-by-functions.md b/functions-and-operators/aggregate-group-by-functions.md
@@ -176,4 +176,4 @@ group by id, val;
 
 ## Related system variables
 
-The [`group_concat_max_len`](/system-variables.md#group_concat_max_len) variable sets the maximum number of items for the `GROUP_CONCAT()` function.
+The [`group_concat_max_len`](/system-variables.md#group_concat_max_len) variable sets the maximum number of items for the `GROUP_CONCAT()` function.
diff --git a/functions-and-operators/bit-functions-and-operators.md b/functions-and-operators/bit-functions-and-operators.md
@@ -300,11 +300,11 @@ The `>>` operator can also be useful for extracting specific parts of a larger n
 
 ## MySQL compatibility
 
-There are some differences between MySQL 8.0 and earlier versions of MySQL in handling bit functions and operators. TiDB aims to follow the behavior of MySQL 8.0.
+There are some differences between MySQL 8.0 and earlier versions of MySQL in handling bit functions and operators. TiDB aims to follow the behavior of MySQL 8.x.
 
 ## Known issues
 
-In the following cases, the query results in TiDB are the same as MySQL 5.7 but different from MySQL 8.0.
+In the following cases, the query results in TiDB are the same as MySQL 5.7 but different from MySQL 8.x.
 
 - Bitwise operations with binary arguments. For more information, see [#30637](https://github.com/pingcap/tidb/issues/30637).
 - The result of the `BIT_COUNT()` function. For more information, see [#44621](https://github.com/pingcap/tidb/issues/44621).
diff --git a/functions-and-operators/encryption-and-compression-functions.md b/functions-and-operators/encryption-and-compression-functions.md
@@ -426,4 +426,4 @@ Examples:
 
 * TiDB does not support the `STATEMENT_DIGEST()` and `STATEMENT_DIGEST_TEXT()` functions.
 * TiDB does not support the `kdf_name`, `salt`, and `iterations` arguments for [`AES_ENCRYPT()`](#aes_encrypt) and [`AES_DECRYPT`](#aes_decrypt) that MySQL added in MySQL 8.0.30.
-* MySQL does not implement the [`SM3()`](#sm3) function.
+* MySQL does not implement the [`SM3()`](#sm3) function.
diff --git a/mysql-compatibility.md b/mysql-compatibility.md
@@ -8,13 +8,13 @@ aliases: ['/docs/dev/mysql-compatibility/','/docs/dev/reference/mysql-compatibil
 
 <CustomContent platform="tidb">
 
-TiDB is highly compatible with the MySQL protocol and the common features and syntax of MySQL 5.7 and MySQL 8.0. The ecosystem tools for MySQL (PHPMyAdmin, Navicat, MySQL Workbench, DBeaver and [more](/develop/dev-guide-third-party-support.md#gui)) and the MySQL client can be used for TiDB.
+TiDB is highly compatible with the MySQL protocol and the common features and syntax of MySQL 8.x. The ecosystem tools for MySQL (PHPMyAdmin, Navicat, MySQL Workbench, DBeaver and [more](/develop/dev-guide-third-party-support.md#gui)) and the MySQL client can be used for TiDB.
 
 </CustomContent>
 
 <CustomContent platform="tidb-cloud">
 
-TiDB is highly compatible with the MySQL protocol and the common features and syntax of MySQL 5.7 and MySQL 8.0. The ecosystem tools for MySQL (PHPMyAdmin, Navicat, MySQL Workbench, DBeaver and [more](https://docs.pingcap.com/tidb/stable/dev-guide-third-party-support#gui)) and the MySQL client can be used for TiDB.
+TiDB is highly compatible with the MySQL protocol and the common features and syntax of MySQL 8.x. The ecosystem tools for MySQL (PHPMyAdmin, Navicat, MySQL Workbench, DBeaver and [more](https://docs.pingcap.com/tidb/stable/dev-guide-third-party-support#gui)) and the MySQL client can be used for TiDB.
 
 </CustomContent>
 
@@ -234,21 +234,21 @@ TiDB supports most [SQL modes](/sql-mode.md):
 
 ### Default differences
 
-TiDB has default differences when compared with MySQL 5.7 and MySQL 8.0:
+TiDB has default differences when compared with MySQL 5.7 and MySQL 8.x:
 
 - Default character set:
     - TiDB's default value is `utf8mb4`.
     - MySQL 5.7's default value is `latin1`.
-    - MySQL 8.0's default value is `utf8mb4`.
+    - MySQL 8.x's default value is `utf8mb4`.
 - Default collation:
     - TiDB's default collation is `utf8mb4_bin`.
     - MySQL 5.7's default collation is `utf8mb4_general_ci`.
-    - MySQL 8.0's default collation is `utf8mb4_0900_ai_ci`.
+    - MySQL 8.x's default collation is `utf8mb4_0900_ai_ci`.
 - Default SQL mode:
     - TiDB's default SQL mode includes these modes: `ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION`.
     - MySQL's default SQL mode:
         - The default SQL mode in MySQL 5.7 is the same as TiDB.
-        - The default SQL mode in MySQL 8.0 includes these modes: `ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION`.
+        - The default SQL mode in MySQL 8.x includes these modes: `ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION`.
 - Default value of `lower_case_table_names`:
     - The default value in TiDB is `2`, and only `2` is currently supported.
     - MySQL defaults to the following values:
@@ -259,7 +259,7 @@ TiDB has default differences when compared with MySQL 5.7 and MySQL 8.0:
     - The default value in TiDB is `ON`, and only `ON` is currently supported.
     - MySQL defaults to the following values:
         - For MySQL 5.7: `OFF`.
-        - For MySQL 8.0: `ON`.
+        - For MySQL 8.x: `ON`.
 
 ### Date and Time
 
diff --git a/optimizer-hints.md b/optimizer-hints.md
@@ -1189,4 +1189,4 @@ mysql> SELECT /*+ SET_VAR(MAX_EXECUTION_TIME=123) */ @@MAX_EXECUTION_TIME, a FRO
 |                  123 | 1 |
 +----------------------+---+
 1 row in set (0.00 sec)
-```
+```
diff --git a/privilege-management.md b/privilege-management.md
@@ -6,7 +6,7 @@ aliases: ['/docs/dev/privilege-management/','/docs/dev/reference/security/privil
 
 # Privilege Management
 
-TiDB supports MySQL 5.7's privilege management system, including the syntax and privilege types. The following features from MySQL 8.0 are also supported:
+TiDB supports MySQL 5.7's privilege management system, including the syntax and privilege types. The following features from MySQL 8.x are also supported:
 
 * SQL Roles, starting with TiDB 3.0.
 * Dynamic privileges, starting with TiDB 5.1.
diff --git a/security-compatibility-with-mysql.md b/security-compatibility-with-mysql.md
@@ -6,7 +6,7 @@ aliases: ['/docs/dev/security-compatibility-with-mysql/','/docs/dev/reference/se
 
 # Security Compatibility with MySQL
 
-TiDB supports security features similar to MySQL 5.7, and also supports some security features of MySQL 8.0. The security features of TiDB are different from MySQL in implementation.
+TiDB supports security features similar to MySQL 5.7, and also supports some security features of MySQL 8.x. The security features of TiDB are different from MySQL in implementation.
 
 ## Unsupported security features
 
@@ -35,37 +35,37 @@ The expiration mechanism of TiDB is different from MySQL in the following aspect
 
 The password complexity policies of TiDB and MySQL have the following differences:
 
-- MySQL v5.7 implements the password complexity policy by using the `validate_password` plugin.
-- MySQL v8.0 re-implements the password complexity policy by using the `validate_password` component.
+- MySQL 5.7 implements the password complexity policy by using the `validate_password` plugin.
+- MySQL 8.x re-implements the password complexity policy by using the `validate_password` component.
 - TiDB introduces a built-in password complexity management feature starting from v6.5.0.
 
 The feature implementation has the following differences:
 
 - Enable the feature:
 
-    - In MySQL v5.7, the feature is implemented by using the `validate_password` plugin. You can enable the feature by installing the plugin.
-    - In MySQL v8.0, the feature is implemented by using the `validate_password` component. You can enable the feature by installing the component.
+    - In MySQL 5.7, the feature is implemented by using the `validate_password` plugin. You can enable the feature by installing the plugin.
+    - In MySQL 8.x, the feature is implemented by using the `validate_password` component. You can enable the feature by installing the component.
     - For TiDB, this feature is built-in. You can enable the feature using the system variable [`validate_password.enable`](/system-variables.md#validate_passwordenable-new-in-v650).
 
 - Dictionary check:
 
-    - In MySQL v5.7, you can specify a file path using the `validate_password_dictionary_file` variable. The file contains a list of words that are not allowed to exist in passwords.
-    - In MySQL v8.0, you can specify a file path using the `validate_password.dictionary_file` variable. The file contains a list of words that are not allowed to exist in passwords.
+    - In MySQL 5.7, you can specify a file path using the `validate_password_dictionary_file` variable. The file contains a list of words that are not allowed to exist in passwords.
+    - In MySQL 8.x, you can specify a file path using the `validate_password.dictionary_file` variable. The file contains a list of words that are not allowed to exist in passwords.
     - In TiDB, you can specify a string using the [`validate_password.dictionary`](/system-variables.md#validate_passworddictionary-new-in-v650) system variable. The string contains a list of words that are not allowed to exist in passwords.
 
 ### Password failure tracking
 
 The password failure tracking policies of TiDB and MySQL have the following differences:
 
-- MySQL v5.7 does not support password failure tracking.
-- MySQL v8.0 supports password failure tracking.
+- MySQL 5.7 does not support password failure tracking.
+- MySQL 8.x supports password failure tracking.
 - TiDB supports password failure tracking starting from v6.5.0.
 
 Because the number of failed attempts and lock status of accounts need to be globally consistent, and as a distributed database, TiDB cannot record the number of failed attempts and lock status in the server memory like MySQL, so the implementation mechanisms are different between TiDB and MySQL.
 
 - For users that are not locked automatically, the count of failed attempts is reset in the following scenarios:
 
-    + MySQL 8.0:
+    + MySQL 8.x:
 
         - When the server is restarted, the count of failed attempts for all accounts is reset.
         - When `FLUSH PRIVILEGES` is executed, the count of failed attempts for all accounts is reset.
@@ -79,7 +79,7 @@ Because the number of failed attempts and lock status of accounts need to be glo
 
 - For users that are locked automatically, the count of failed attempts is reset in the following scenarios:
 
-    + MySQL 8.0:
+    + MySQL 8.x:
 
         - When the server is restarted, the temporary locking for all accounts is reset.
         - When `FLUSH PRIVILEGES` is executed, the temporary locking for all accounts is reset.
@@ -95,8 +95,8 @@ Because the number of failed attempts and lock status of accounts need to be glo
 
 The password reuse policies of TiDB and MySQL have the following differences:
 
-- MySQL v5.7 does not support password reuse management.
-- MySQL v8.0 supports password reuse management.
+- MySQL 5.7 does not support password reuse management.
+- MySQL 8.x supports password reuse management.
 - TiDB supports password reuse management starting from v6.5.0.
 
 The implementation mechanisms are consistent between TiDB and MySQL. Both use the `mysql.password_history` system table to implement the password reuse management feature. However, when deleting a user that does not exist in the `mysql.user` system table, TiDB and MySQL have different behaviors:
@@ -258,4 +258,4 @@ To configure and use `tidb_auth_token` as the authentication method for TiDB Sel
 
     If an incorrect `--sub` is specified when the token is generated (such as `--sub "wronguser@pingcap.com"`), the authentication using this token would fail.
 
-You can encode and decode a token using the debugger provided by [jwt.io](https://jwt.io/).
+You can encode and decode a token using the debugger provided by [jwt.io](https://jwt.io/).
diff --git a/sql-statements/sql-statement-select.md b/sql-statements/sql-statement-select.md
@@ -232,7 +232,7 @@ In this example, you can find the query result in `/tmp/tmp_file3` as follows:
 
 - The syntax `SELECT ... INTO @variable` is not supported.
 - The syntax `SELECT ... INTO DUMPFILE` is not supported.
-- The syntax `SELECT .. GROUP BY expr` does not imply `GROUP BY expr ORDER BY expr` as it does in MySQL 5.7. TiDB instead matches the behavior of MySQL 8.0 and does not imply a default order.
+- The syntax `SELECT .. GROUP BY expr` does not imply `GROUP BY expr ORDER BY expr` as it does in MySQL 5.7. TiDB instead matches the behavior of MySQL 8.x and does not imply a default order.
 - The syntax `SELECT ... TABLESAMPLE ...` is a TiDB extension designed for compatibility with other database systems and the [ISO/IEC 9075-2](https://standards.iso.org/iso-iec/9075/-2/ed-6/en/) standard, but currently it is not supported by MySQL.
 
 ## See also
diff --git a/tidb-cloud/key-concepts.md b/tidb-cloud/key-concepts.md
@@ -21,7 +21,7 @@ TiDB provides complete distributed transactions, and the model has some optimiza
 
 ## SQL
 
-TiDB is highly compatible with the MySQL protocol and the common features and syntax of MySQL 5.7 and MySQL 8.0. [Learn more about SQL in TiDB Cloud](/tidb-cloud/sql-concepts.md).
+TiDB is highly compatible with the MySQL protocol and the common features and syntax of MySQL 5.7 and MySQL 8.x. [Learn more about SQL in TiDB Cloud](/tidb-cloud/sql-concepts.md).
 
 ## AI features
 
@@ -56,4 +56,4 @@ TiDB Cloud offers automated backup solutions and point-in-time recovery (PITR) c
 
 ## Security
 
-TiDB Cloud provides a robust and flexible security framework designed to protect data, enforce access control, and meet modern compliance standards. [Learn more about security](/tidb-cloud/security-concepts.md).
+TiDB Cloud provides a robust and flexible security framework designed to protect data, enforce access control, and meet modern compliance standards. [Learn more about security](/tidb-cloud/security-concepts.md).
diff --git a/tidb-cloud/security-concepts.md b/tidb-cloud/security-concepts.md
diff --git a/tidb-cloud/sql-concepts.md b/tidb-cloud/sql-concepts.md
diff --git a/tidb-cloud/tidb-cloud-faq.md b/tidb-cloud/tidb-cloud-faq.md
diff --git a/tidb-lightning/tidb-lightning-checkpoints.md b/tidb-lightning/tidb-lightning-checkpoints.md
diff --git a/tidb-troubleshooting-map.md b/tidb-troubleshooting-map.md

Original file line number	Diff line number	Diff line change
`@@ -47,8 +47,7 @@ Regardless of the migration mode you choose, the precheck always includes the fo`
`47`	`47`
`48`	`48`	`> Warning:`
`49`	`49`	`>`
`50`		`- > - Migrating data from MySQL 8.0 to TiDB using DM is an experimental feature (introduced since DM v2.0). It is NOT recommended that you use it in a production environment.`
`51`		`- > - Migrating data from MariaDB to TiDB using DM is an experimental feature. It is NOT recommended that you use it in a production environment.`
	`50`	`+ > Migrating data from MariaDB to TiDB using DM is an experimental feature. It is NOT recommended that you use it in a production environment.`
`52`	`51`
`53`	`52`	`- Compatibility of the upstream MySQL table schema`
`54`	`53`
Original file line number	Diff line number	Diff line change
`@@ -176,4 +176,4 @@ group by id, val;`
`176`	`176`
`177`	`177`	`## Related system variables`
`178`	`178`
`179`		-The [`group_concat_max_len`](/system-variables.md#group_concat_max_len) variable sets the maximum number of items for the `GROUP_CONCAT()` function.
	`179`	+The [`group_concat_max_len`](/system-variables.md#group_concat_max_len) variable sets the maximum number of items for the `GROUP_CONCAT()` function.