out system variable, which automatically terminates long-running idle transactions. When a user session in a transactional state remains idle for a duration exceeding the value of this variable, TiDB will statements. You can use this variable to get the resource consumption of the last statement in the session. • Add database metrics based on resource groups: QPS/TPS, execution time (P999/P99/P95), number �→ Newly added Controls the idle time- out for trans- actions in a user ses- sion. When a user session is in a trans- ac- tional state and re- mains idle for a dura- tion exceed- ing the value of this

cache allows all sessions within the same TiDB �→ instance to share the plan cache. Compared with session-level plan �→ cache, this feature reduces SQL compilation time by caching more �→ execution plans possibility of execution plan mutations, and maintains stable cluster performance. Compared with session-level ex- ecution plan cache, instance-level execution plan cache offers the following advantages: to move identified runaway queries to this group. Meanwhile, subsequent queries within the same session will continue to execute in the original resource group. By switching resource groups, you can manage

cache allows all sessions within the same TiDB �→ instance to share the plan cache. Compared with session-level plan �→ cache, this feature reduces SQL compilation time by caching more �→ execution plans possibility of execution plan mutations, and maintains stable cluster performance. Compared with session-level ex- ecution plan cache, instance-level execution plan cache offers the following advantages: to move identified runaway queries to this group. Meanwhile, subsequent queries within the same session will continue to execute in the original resource group. By switching resource groups, you can manage

the current session, and tables schemas are not persistent. * Supports duplicated table names. You do not need to design complicated naming rules for your application. 42 * Provides session-level data triggered out of the specified time when a new index is added #28698 – Fix a bug that setting any session variable invalidates tidb_snapshot #28683 – Fix a bug that BR is not working for clusters with many configure max_memory_usage as follows: [profiles.default] max_memory_usage = 10000000000000 Set session variables with the following SQL statements: set @@tidb_isolation_read_engines='tiflash'; set @@tidb_allow_mpp=1;

REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • Descending Index #2519 • SKIP LOCKED syntax #18207 zshrc from the output of Step 1. source ${your_shell_profile} 3. Start the cluster in the current session: • To start a TiDB cluster of the latest version with 1 TiDB instance, 1 TiKV instance, 1 PD instance --tag �→ playground .... For details, refer to the TiUP Reference guide. 4. Start a new session to access TiDB: • Use the TiUP client to connect to TiDB. tiup client • Alternatively, you can

INFORMATION_SCHEMA.PROCESSLIST and INFORMATION_SCHEMA.CLUSTER_ �→ PROCESSLIST system tables add the SESSION_ALIAS field to show the number of rows currently affected by the DML statement #46889 @lcwangchao REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • Descending Index #2519 • SKIP LOCKED syntax #18207 zshrc from the output of Step 1. source ${your_shell_profile} 3. Start the cluster in the current session: 92 Note: • For the playground operated in the following way, after the deploy- ment and testing

and INFORMATION_SCHEMA.CLUSTER_ �→ PROCESSLIST system tables add the SESSION_ALIAS field to show the alias of the current session. #46889 @lcwangchao 2.2.2.6 Compiler versions • To improve the TiFlash REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • Descending Index #2519 • SKIP LOCKED syntax #18207 zshrc from the output of Step 1. source ${your_shell_profile} 3. Start the cluster in the current session: 89 Note: • For the playground operated in the following way, after the deploy- ment and testing

clusters use the new default values, which means Prepared Plan Cache is enabled by default and each session can cache 100 plans at most (capacity=100). For the memory consumption of this feature, see memory REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” 2.6.2 Features that are different from MySQL 2.6.2 from the output of Step 1. 113 source ${your_shell_profile} 3. Start the cluster in the current session: • If you want to start a TiDB cluster of the latest version with 1 TiDB instance, 1 TiKV instance

REPAIR TABLE syntax • OPTIMIZE TABLE syntax • HANDLER statement • CREATE TABLESPACE statement • “Session Tracker: Add GTIDs context to the OK packet” • Descending Index #2519 • SKIP LOCKED syntax #18207 zshrc from the output of Step 1. source ${your_shell_profile} 3. Start the cluster in the current session: 89 Note: • For the playground operated in the following way, after the deploy- ment and testing TiDB supports running tiup playground on the machine that uses the Apple M1 chip. 4. Start a new session to access TiDB: • Use the TiUP client to connect to TiDB. 90 tiup client • Alternatively, you

the replication with MinIO #1463 * Set the default value of the explicit_defaults_for_timestamp session vari- able to ON to make the MySQL 5.7 downstream keep the same behavior with the upstream TiDB #1585 configure max_memory_usage as follows: [profiles.default] max_memory_usage = 10000000000000 Set session variables with the following SQL statements: set @@tidb_isolation_read_engines='tiflash'; set @@tidb_allow_mpp=1; source command according to the path. source .bash_profile 3. Start the cluster in the current session: • If you want to start a TiDB cluster of the latest version with 1 TiDB instance, 1 TiKV instance