grows, the decision-making leaders need to understand the business status of the entire company to make decisions in time. In this case, the company needs to aggregate the scattered data into the same system region-split-size to set Re- gions to a larger size. This can effectively reduce the number of Regions, make Regions easier to manage, and improve the cluster performance and stability. User document, #11515 dynamically In earlier TiDB versions, after modifying a configuration item, you must restart the cluster to make the modification effective. This might interrupt online services. To address this issue, TiDB v6.1

grows, the decision-making leaders need to understand the business status of the entire company to make decisions in time. In this case, the company needs to aggregate the scattered data into the same system recovery (PITR) along with cdclog. Since v5.4.0, cdclog-based PITR and cdclog are no longer supported. • Make the behavior of setting system variables to the “DEFAULT” more MySQL- compatible #29680 • Set the Engine in v5.4.0 is not compatible with previous versions. Before upgrading the cluster, you need to make sure that Raft Engine on all TiKV nodes is disabled. It is recommended to use Raft Engine only in

grows, the decision-making leaders need to understand the business status of the entire company to make decisions in time. In this case, the company needs to aggregate the scattered data into the same system execute only swapoff -a, swap will be enabled again after you restart the system. • sysctl -p is to make the configuration effective without restarting the system. 121 4.2.3 Check and stop the firewall the following result, the chronyd service is not running normally: 506 Cannot talk to daemon To make the NTP service start synchronizing as soon as possible, run the following command. Replace pool.ntp

auto-incremental column values (IDs) are globally unique and incremen- tal within a single TiDB server. To make the IDs incremental among multiple TiDB servers, you can use the AUTO_INCREMENT MySQL compatibility TiDB This document briefly introduces how to use TiDB’s CURD SQL. 4.2.2.1 Before you start Please make sure you are connected to a TiDB cluster. If not, refer to Build a TiDB Serverless Cluster to create Run the code and check the result 122 1. Execute the following command to run the sample code: make 2. Check the Expected-Output.txt to see if the output matches. 4.3.1.1.3 Sample code snippets You

grows, the decision-making leaders need to understand the business status of the entire company to make decisions in time. In this case, the company needs to aggregate the scattered data into the same system with PITR (Point-in-time recovery) either. When using the index acceleration feature, you need to make sure that no PITR backup task is running in the background; otherwise, unexpected results might occur depre- cated and replaced by Metadata Lock. 2.2.4 Improvements • TiDB • For BIT and CHAR columns, make the result of INFORMATION_SCHEMA.COLUMNS consistent with MySQL #25472 @hawkingrei • Optimize the

MAX_EXECUTION_TIME to make it compatible with MySQL #43031 @dveeden • Support using the MergeSort operator on partitioned tables in IndexLookUp #26166 @Defined2014 • Enhance caching_sha2_password to make it compatible auto-incremental column values (IDs) are globally unique and incremen- tal within a single TiDB server. To make the IDs incremental among multiple TiDB servers, you can use the AUTO_INCREMENT MySQL compatibility TiDB This document briefly introduces how to use TiDB’s CURD SQL. 4.2.2.1 Before you start Please make sure you are connected to a TiDB cluster. If not, refer to Build a TiDB Serverless Cluster to create

behavior of the LOAD DATA statement varies in different TiDB versions before v7.6.0, so you might need to make additional ad- justments when using this statement. Specifically, before v4.0.0, LOAD DATA commits large error. In this case, you need to manually modify the TiDB configuration file and restart TiDB to make the modification take effect. To reduce your management overhead, TiDB v7.6.0 introduces the system auto-incremental column values (IDs) are globally unique and incremen- tal within a single TiDB server. To make the IDs incremental among multiple TiDB servers, you can use the AUTO_INCREMENT MySQL compatibility

able memory of the BR process to avoid OOM when using BR for backup and restore #53777 @Leavrth • Make incremental backups compatible with point-in-time recovery (PITR) #54474 @3pointer • Support backing auto-incremental column values (IDs) are globally unique and incremen- tal within a single TiDB server. To make the IDs incremental among multiple TiDB servers, you can use the AUTO_INCREMENT MySQL compatibility TiDB This document briefly introduces how to use TiDB’s CURD SQL. 4.2.2.1 Before you start Please make sure you are connected to a TiDB cluster. If not, refer to Build a TiDB Serverless Cluster to create

indexes. Note that TiDB vector search indexes rely on TiFlash. Before using vector search indexes, make sure that TiFlash nodes are deployed in your TiDB cluster. For more information, see documentation auto-incremental column values (IDs) are globally unique and incremen- tal within a single TiDB server. To make the IDs incremental among multiple TiDB servers, you can use the AUTO_INCREMENT MySQL compatibility TiDB This document briefly introduces how to use TiDB’s CURD SQL. 4.2.2.1 Before you start Please make sure you are connected to a TiDB cluster. If not, refer to Build a TiDB Cloud Serverless Cluster to

indexes. Note that TiDB vector search indexes rely on TiFlash. Before using vector search indexes, make sure that TiFlash nodes are deployed in your TiDB cluster. For more information, see documentation auto-incremental column values (IDs) are globally unique and incremen- tal within a single TiDB server. To make the IDs incremental among multiple TiDB servers, you can use the AUTO_INCREMENT MySQL compatibility TiDB This document briefly introduces how to use TiDB’s CURD SQL. 4.2.2.1 Before you start Please make sure you are connected to a TiDB cluster. If not, refer to Build a TiDB Cloud Serverless Cluster to