storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node sup- ports a maximum of 1,000 concurrencies, and the maximum detection strategy for both logical and physical import modes via the conflict.strategy parameter. The duplicate-resolution parameter for the old version of conflict detection will be removed in a future release table causes TiDB to crash #55970 @D3Hunter • Fix the issue that adding a unique index causes the duplicate entry error #56161 @tangenta • Fix the issue that TiDB Lightning does not ingest all KV pairs

storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node sup- ports a maximum of 1,000 concurrencies, and the maximum detection strategy for both logical and physical import modes via the conflict.strategy parameter. The duplicate-resolution parameter for the old version of conflict detection will be removed in a future release table causes TiDB to crash #55970 @D3Hunter • Fix the issue that adding a unique index causes the duplicate entry error #56161 @tangenta • Fix the issue that TiDB Lightning does not ingest all KV pairs

storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node sup- ports a maximum of 1,000 concurrencies, and the maximum LIMIT might not be pushed down to the OR type Index Merge #48588 @AilinKid • Fix the issue that duplicate built-in rows might exist in the mysql.bind_info table after BR import #46527 @qw4990 • Fix the 5.2 5.1 5.0 4.0 Basic SELECT, INSERT, UPDATE, DELETE, REPLACE Y Y Y Y Y Y Y Y Y Y Y INSERT ON DUPLICATE KEY UPDATE Y Y Y Y Y Y Y Y Y Y Y LOAD DATA INFILE Y Y Y Y Y Y Y Y Y Y Y SELECT INTO OUTFILE Y Y

storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node sup- ports a maximum of 1,000 concurrencies, and the maximum 3 5.2 5.1 5.0 4.0 Basic SELECT, INSERT, UPDATE, DELETE, REPLACE Y Y Y Y Y Y Y Y Y Y INSERT ON DUPLICATE KEY UPDATE Y Y Y Y Y Y Y Y Y Y LOAD DATA INFILE Y Y Y Y Y Y Y Y Y Y SELECT INTO OUTFILE Y Y Y Y N N N N N N N N N 2.3.9 Security Security 7.5 7.1 6.5 6.1 5.4 5.3 5.2 5.1 5.0 4.0 Transparent layer security (TLS) Y Y Y Y Y Y Y Y Y Y Encryption at rest (TDE) Y Y Y Y Y Y Y Y Y Y Role-based authentication

storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node sup- ports a maximum of 1,000 concurrencies, and the maximum This feature simplifies TiProxy deployment and �→ reduces the complexity of the database access layer. 2.2.1 Feature details 2.2.1.1 Performance • The optimizer allows pushing the Projection operator detection strategy for both logical and physical import modes via the conflict.strategy parameter. The duplicate-resolution parameter for the old version of conflict detection will be removed in a future release

enables you to scale out or scale in the computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node supports a maximum of 1,000 concurrencies, and the maximum showing the size of the backup and restore data when backing up and restoring data in the SQL logical layer #27247 – Improve the default collection logic of ANALYZE when tidb_analyze_version is 2, which accelerates instance unexpectedly exits #3061 * Fix the issue that TiCDC process might panic when TiKV sends duplicate requests to the same Region #2386 * Fix unnecessary CPU consumption when verifying downstream TiD-

storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node sup- ports a maximum of 1,000 concurrencies, and the maximum detection strategy for both logical and physical import modes via the conflict.strategy parameter. The duplicate-resolution parameter for the old version of conflict detection will be removed in a future release cause TiFlash to crash in some corner cases #9116 @wshwsh12 • Fix the issue that a large number of duplicate rows might be read in FastScan mode after importing data via BR or TiDB Lightning #9118 @JinheLin

storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node sup- ports a maximum of 1,000 concurrencies, and the maximum from cgroup v1: open /sys/memory.stat no such file or directory” #42659 @hawkingrei • Fix the Duplicate Key issue that occurs when updating the partition key of a row on a partitioned table with a global resolves locks #43243 @MyonKeminta • Fix the issue that the LOCK to PUT optimization leads to duplicate data being 83 returned in specific queries #28011 @zyguan • Fix the issue that when data is changed

enables you to scale out or scale in the computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node supports a maximum of 1,000 concurrencies, and the maximum performance �→ .tcp-no �→ -delay Newly added Determines whether to enable TCP_NODELAY at the TCP layer. The default value is true, which means TCP_NODELAY is enabled. TiDB con- figuration file performance ANSI_QUOTES #24429 – Forbid statements such as INSERT INTO table PARTITION ()... �→ ON DUPLICATE KEY UPDATE to read data from non-listed partitions #24746 – Fix the potential index out of range

storage architecture, enabling easy scaling of computing or storage capacity separately. The computing layer supports a maximum of 512 nodes, each node sup- ports a maximum of 1,000 concurrencies, and the maximum authentication (introduced in v8.1.0) TiCDC supports client authentication using mutual Transport Layer �→ Security (mTLS) or TiDB username and password. This feature enables �→ CLI or OpenAPI clients to require client authentication using client certificates, thereby establishing mutual Transport Layer Security (mTLS). Additionally, you can configure authentication based on TiDB username and password