code repository. Now DM follows TiDB in version numbers. Next to v2.0.x, the new DM version is v5.3.0, and you can upgrade from v2.0.x to v5.3.0 without any risk. 41 • The default deployed version of Prometheus other than utf8, utf8mb4, ascii, latin1 and binary • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Savepoints #6840 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase port needed by the TiDB cluster nodes • Currently, the TiUP cluster supports deploying TiDB on the x86_64 (AMD64) and ARM architectures: – It is recommended to use CentOS 7.3 or later versions on AMD64

pay attention to the following restrictions: – Index Merge supports only disjunctive normal form (X1 ￿ X2 ￿ …Xn). That is, this feature only works when filtering conditions in a WHERE clause are connected issue of the tidb_analyze_version value change that occurs when up- grading the cluster from v4.x to v5.x #25422 – Fix the issue of the wrong result that occurs when using different collations in a subquery than ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Savepoints #6840 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase

DM auto �→ - �→ fix �→ - �→ gtid �→ in the task con- fig- u- ra- tion file DeletedDeprecated in v5.x and offi- cially deleted in v6.1.0. 80 Configuration file Configuration Change type Description DM meta �→ - �→ dir �→ and charset �→ in the source con- fig- u- ra- tion file DeletedDeprecated in v5.x and offi- cially deleted in v6.1.0. 2.2.2.3 Others • Enable Prepared Plan Cache by default Prepared than ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Savepoints #6840 • Column-level privileges #9766 103 • XA syntax (TiDB uses a two-phase

effect as result caching (that is, result materialization). For example: INSERT INTO t2 SELECT Mod(x,y) FROM t1; During the experimental phase, this feature is disabled by default. To enable it, you can than ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally port needed by the TiDB cluster nodes • Currently, the TiUP cluster supports deploying TiDB on the x86_64 (AMD64) and ARM architectures: • It is recommended to use CentOS 7.3 or later versions on AMD64

ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions 88 • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally port needed by the TiDB cluster nodes • Currently, the TiUP cluster supports deploying TiDB on the x86_64 (AMD64) and ARM architectures: • It is recommended to use CentOS 7.3 or later versions on AMD64 mysql --version An example of the expected output: mysql Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline �→ 5.1 2. Run the connection string obtained in Step 1. mysql --connect-timeout

improvements, and bug fixes released in 7.2.0-DMR, 7.3.0-DMR, and 7.4.0-DMR. When you upgrade from 7.1.x to 7.5.0, you can download the TiDB Release Notes PDF to view all release notes between the two LTS Previously, it would take the time of X plus the time �→ of Y to execute two ADD INDEX statements simultaneously �→ (X and Y). With this feature, adding two indexes X and Y in one SQL �→ can be concurrently ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions 75 • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally

than ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally port needed by the TiDB cluster nodes • Currently, the TiUP cluster supports deploying TiDB on the x86_64 (AMD64) and ARM architectures: • It is recommended to use CentOS 7.3 or later versions on AMD64 mysql --version An example of the expected output: mysql Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline �→ 5.1 2. Run the connection string obtained in Step 1. mysql --connect-timeout

version, and these issues are fixed in new versions. It is recommended that you use the latest 5.2.x version. In v5.2, the key new features and improvements are as follows: • Support using several functions TopN/Limit. For example, for pagination queries on a large table that contain the order by col limit x con- dition, TiDB can more easily select the right index and reduce query response time. 36 – Improve number of goroutines under high concur- rency #2201 – Dumpling * Support always splitting TiDB v3.x tables through tidb_rowid to save TiDB memory #301 * Reduce access of Dumpling to the information_schema

sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally port needed by the TiDB cluster nodes • Currently, the TiUP cluster supports deploying TiDB on the x86_64 (AMD64) and ARM architectures: • It is recommended to use CentOS 7.3 or later versions on AMD64 mysql --version An example of the expected output: mysql Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline �→ 5.1 2. Run the connection string obtained in Step 1. mysql --connect-timeout

sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally port needed by the TiDB cluster nodes • Currently, the TiUP cluster supports deploying TiDB on the x86_64 (AMD64) and ARM architectures: • It is recommended to use CentOS 7.3 or later versions on AMD64 mysql --version An example of the expected output: mysql Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline �→ 5.1 2. Run the connection string obtained in Step 1. mysql --connect-timeout