When managing hundreds of databases with the same schema, it is often �→ necessary to apply SQL bindings across these databases. For example, �→ in SaaS or PaaS data platforms, each user typically operates SQL for each database one by �→ one. TiDB v7.6.0 introduces cross-database SQL bindings that enable �→ matching bindings across all schema-equivalent databases. 0 码力 | 6123 页 | 107.24 MB | 1 年前

3

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 execution execution plans to improve the efficiency of creating bindings. • The SQL execution plan binding supports more optimizer hints, and optimizes the conversion method for complex execution plans, making variable will be deprecated. • It is planned to redesign the automatic evolution of execution plan bindings in subsequent releases, and the related variables and behavior will change. • In v8.0.0, TiDB introduces

When managing hundreds of databases with the same schema, it is often �→ necessary to apply SQL bindings across these databases. For example, �→ in SaaS or PaaS data platforms, each user typically operates SQL for each database one by �→ one. TiDB v7.6.0 introduces cross-database SQL bindings that enable �→ matching bindings across all schema-equivalent databases. 0 码力 | 6321 页 | 107.46 MB | 1 年前

3

variable will be deprecated. • It is planned to redesign the automatic evolution of execution plan bindings in subse- quent releases, and the related variables and behavior will change. • In v8.0.0, TiDB 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 according to historical execution plans Y Y Y Y Y Y E N N N N N Coprocessor cache Y Y Y Y Y Y Y ployed on a single machine, that is, TiDB and TiKV’s CPU resources are isolated through NUMA node bindings. PD and Prometheus are deployed together, but their data directories need to use separate file systems

variable will be deprecated. • It is planned to redesign the automatic evolution of execution plan bindings in subse- quent releases, and the related variables and behavior will change. • In v8.0.0, TiDB 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 according to historical execution plans Y Y Y Y Y Y E N N N N N Coprocessor cache Y Y Y Y Y Y Y ployed on a single machine, that is, TiDB and TiKV’s CPU resources are isolated through NUMA node bindings. PD and Prometheus are deployed together, but their data directories need to use separate file systems

be removed in a future release. • It is planned to redesign the auto-evolution of execution plan bindings in subsequent releases, and the related variables and behavior will change. 2.2.4 Improvements Path selects duplicated indexes #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 analyze on a partition table might cause TiDB to panic #51187 @hi-rustin • Fix the issue that SQL bindings might not work when IN() in a SQL statement contains a different number of values #51222 @hawkingrei

ployed on a single machine, that is, TiDB and TiKV’s CPU resources are isolated through NUMA node bindings. PD and Prometheus are deployed together, but their data directories need to use separate file systems on-site information: 1030 • TiDB version • TiDB configuration • TiDB session variables • TiDB SQL bindings • The table schema in sql-statement • The statistics of the table in sql-statement • The result import the on-site information of a TiDB cluster to another cluster, the TiDB session variables, SQL bindings, table schemas and statistics of the latter cluster are modified. With an existing ZIP file exported

When managing hundreds of databases with the same schema, it is often �→ necessary to apply SQL bindings across these databases. For example, �→ in SaaS or PaaS data platforms, each user typically operates SQL for each database one by �→ one. TiDB v7.6.0 introduces cross-database SQL bindings that enable �→ matching bindings across all schema-equivalent databases. 0 码力 | 6479 页 | 108.61 MB | 10 月前

3

variable will be deprecated. 53 • It is planned to redesign the auto-evolution of execution plan bindings in subse- quent releases, and the related variables and behavior will change. • The TiDB Lightning 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 Y Y Y Y E N N N N N Coprocessor cache Y Y Y Y Y Y Y Y Y ployed on a single machine, that is, TiDB and TiKV’s CPU resources are isolated through NUMA node bindings. PD and Prometheus are deployed together, but their data directories need to use separate file systems

Non-prepared statement cache Y E N N N N N N N N SQL plan management (SPM) Y Y Y Y Y Y Y Y Y Y Create bindings according to historical execution plans Y Y E N N N N N N N Coprocessor cache Y Y Y Y Y Y Y Y Y ployed on a single machine, that is, TiDB and TiKV’s CPU resources are isolated through NUMA node bindings. PD and Prometheus are deployed together, but their data directories need to use separate file systems database • Restore a table • Restore multiple tables with table filter • Restore execution plan bindings from the mysql schema • Restore encrypted snapshots For more information about snapshot backup