#53040 @RidRisR 55 • Except for the br log restore subcommand, all other br log subcommands support skipping the loading of the TiDB domain data structure to reduce memory consumption #52088 @Leavrth • Support behavior changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments the query performance. In TiDB, creating a secondary index is an online operation, which does not block any data read and write operations on a table. For each index, TiDB creates references for each row

behavior changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments the query performance. In TiDB, creating a secondary index is an online operation, which does not block any data read and write operations on a table. For each index, TiDB creates references for each row this SQL statement. First, check out the books written by the author (ID is 2299112019) in the CTE block books_authored_by_rm. Then find the average rating and order for these books respectively in book

file- �→ size, purge- �→ threshold �→ , recovery- �→ mode, recovery- �→ read- �→ block- �→ size, recovery- �→ read- �→ block- �→ size, and recovery- �→ threads. For details, see TiKV Configura- tion File processes to forward requests �→ , ensure that the value is large enough so that HAProxy does not �→ block processes. daemon # Makes the process fork into �→ background. It is equivalent to the command line processes to forward requests �→ , ensure that the value is large enough so that HAProxy does not �→ block processes. daemon # Makes the process fork into �→ background. It is equivalent to the command line

behavior changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments the query performance. In TiDB, creating a secondary index is an online operation, which does not block any data read and write operations on a table. For each index, TiDB creates references for each row this SQL statement. First, check out the books written by the author (ID is 2299112019) in the CTE block books_authored_by_rm. Then find the average rating and order for these books respectively in book

behavior changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments the query performance. In TiDB, creating a secondary index is an online operation, which does not block any data read and write operations on a table. For each index, TiDB creates references for each row this SQL statement. First, check out the books written by the author (ID is 2299112019) in the CTE block books_authored_by_rm. Then find the average rating and order for these books respectively in book

behavior changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments the query performance. In TiDB, creating a secondary index is an online operation, which does not block any data read and write operations on a table. For each index, TiDB creates references for each row this SQL statement. First, check out the books written by the author (ID is 2299112019) in the CTE block books_authored_by_rm. Then find the average rating and order for these books respectively in book

file Configuration parame- ter Change type Description TiDB Light- ning block- �→ size Newly added Controls the I/O block size for sorting local files in Physical Import Mode (backend �→ =' �→ local addresses to enhance stability #49515 @mittalrishabh • Support configuring the block-size parameter to control the I/O block size for sorting local files to improve performance #45037 @mittalrishabh 2.2 behavior changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments

behavior changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments the query performance. In TiDB, creating a secondary index is an online operation, which does not block any data read and write operations on a table. For each index, TiDB creates references for each row this SQL statement. First, check out the books written by the author (ID is 2299112019) in the CTE block books_authored_by_rm. Then find the average rating and order for these books respectively in book

the Titan engine #16245 @Connor1996 38 • Enable the shared cache for Titan blob files and RocksDB block files by default (shared-blob-cache defaults to true), eliminating the need to configure blob- �→ cache �→ Newly added Controls whether to enable the shared cache for Titan blob files and RocksDB block files. The default value is true. 68 Configuration file Configuration parame- ter Change type Description behavior changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments

behavior changes in MySQL compatibility mode, where there is no shared allocator and therefore no skipping of numbers. Note: The AUTO_INCREMENT attribute might cause hotspot in production environ- ments the query performance. In TiDB, creating a secondary index is an online operation, which does not block any data read and write operations on a table. For each index, TiDB creates references for each row this SQL statement. First, check out the books written by the author (ID is 2299112019) in the CTE block books_authored_by_rm. Then find the average rating and order for these books respectively in book