statement might report an error or not take effect #55666 @time-and-fate • Fix the issue that a SQL binding containing window functions might not take effect in some cases #55981 @winoros • Fix the issue cache E N N N N N N N N N N N SQL binding Y Y Y Y Y Y Y Y Y Y Y Y 93 Advanced SQL features 8.4 8.3 8.2 8.1 7.5 7.1 6.5 6.1 5.4 5.3 5.2 5.1 Cross-database binding Y Y Y Y N N N N N N N N Create bindings Supported metadata types 518 Each document in the TiDB vector store can be paired with metadata, structured as key-value pairs within a JSON object. Keys are always strings, while values can be any of the

statement might report an error or not take effect #55666 @time-and-fate • Fix the issue that a SQL binding containing window functions might not take effect in some cases #55981 @winoros • Fix the issue cache E N N N N N N N N N N N SQL binding Y Y Y Y Y Y Y Y Y Y Y Y 88 Advanced SQL features 8.4 8.3 8.2 8.1 7.5 7.1 6.5 6.1 5.4 5.3 5.2 5.1 Cross-database binding Y Y Y Y N N N N N N N N Create bindings Supported metadata types 513 Each document in the TiDB vector store can be paired with metadata, structured as key-value pairs within a JSON object. Keys are always strings, while values can be any of the

Enhance SQL execution plan binding #55280 #55343 @time-and-fate In OLTP scenarios, the optimal execution plan for most SQL statements is fixed. Imple- menting SQL execution plan binding for important SQL statements large number of SQL execution plan bindings, TiDB enhances the capability and experience of SQL binding, including: • Use a single SQL statement to create SQL execution plan bindings from multiple historical creating bindings. • The SQL execution plan binding supports more optimizer hints, and optimizes the conversion method for complex execution plans, making the binding more stable in restoring the execution

Cross-database SQL binding (introduced in v7 �→ .6.0) When managing hundreds of databases with the cache Y Y Y Y Y Y Y E E Non-prepared statement cache Y Y E N N N N N N SQL binding Y Y Y Y Y Y Y Y Y Cross-database binding Y N N N N N N N N Create bindings according to historical execution plans Y tools to prevent the competition for CPU resources which might cause reduced performance. Note: • Binding cores using NUMA is a method to isolate CPU resources and is suitable for deploying multiple instances

Y Y Y Y Y Y Y Y E E Non-prepared statement cache Y Y Y E N N N N N N SQL binding Y Y Y Y Y Y Y Y Y Y Cross-database binding Y Y N N N N N N N N Create bindings according to historical execution plans tools to prevent the competition for CPU resources which might cause reduced performance. Note: • Binding cores using NUMA is a method to isolate CPU resources and is suitable for deploying multiple instances configure the labels type for PD: pd: replication.location-labels: ["host"] • numa_node core binding • In the instance parameter module, configure the corresponding numa_node param- eter and add the

Cross-database SQL binding (introduced in v7 �→ .6.0) When managing hundreds of databases with the cache Y Y Y Y Y Y Y E E Non-prepared statement cache Y Y E N N N N N N SQL binding Y Y Y Y Y Y Y Y Y Cross-database binding Y N N N N N N N N Create bindings according to historical execution plans Y tools to prevent the competition for CPU resources which might cause reduced performance. Note: • Binding cores using NUMA is a method to isolate CPU resources and is suitable for deploying multiple instances

using CREATE �→ �→ TABLE �→ . 58 Variable name Change type Description tidb_ �→ load �→ _ �→ binding �→ _ �→ timeout �→ Newly added Controls the time- out of loading bind- ings. If the ex- ecution @hawkingrei • Fix the issue that when executing the CREATE GLOBAL BINDING statement, if the schema name is in uppercase, the binding does not take effect #50646 @qw4990 • Fix the issue that Index Path #50496 @AilinKid • Fix the issue that PLAN REPLAYER fails to load bindings when the CREATE GLOBAL �→ BINDING statement contains IN() #43192 @King-Dylan • Fix the issue that when multiple analyze tasks fail

Cross-database SQL binding When managing hundreds of databases with the same schema, it is often For more information, see documentation. 2.2.1.3 Reliability • Cross-database execution plan binding #48875 @qw4990 When running SaaS services on TiDB, it is common practice to store data for each execution plan binding for a SQL statement, this binding usually applies to the SQL statements in other databases as well. For this scenario, TiDB v7.6.0 introduces the cross-database binding feature, which

tools to prevent the competition for CPU resources which might cause reduced performance. Note: • Binding cores using NUMA is a method to isolate CPU resources and is suitable for deploying multiple instances configure the labels type for PD: pd: replication.location-labels: ["host"] • numa_node core binding • In the instance parameter module, configure the corresponding numa_node param- eter and add the --log-file restore_system_table.log After the restore is completed, you can confirm the execution plan binding information with SHOW GLOBAL BINDINGS: SHOW GLOBAL BINDINGS; 906 The dynamic loading of execution

if you create a SQL binding for an execution plan that has been cached via Plan Cache, the binding invalidates the plan already cached for the corresponding query. The new binding does not affect execution tools to prevent the competition for CPU resources which might cause reduced performance. Note: • Binding cores using NUMA is a method to isolate CPU resources and is suitable for deploying multiple instances configure the labels type for PD: pd: replication.location-labels: ["host"] • numa_node core binding 160 – In the instance parameter module, configure the corresponding numa_node param- eter and add