You are viewing the documentation of TiDB v6.0 (DMR). PingCAP does not provide bug fixes for v6.0. Any bugs will be fixed in future releases.

For general purposes, please use the latest LTS version of the TiDB database.

SQL Physical Optimization

Physical optimization is cost-based optimization, which makes a physical execution plan for the logical execution plan generated in the previous stage. In this stage, the optimizer selects a specific physical implementation for each operator in the logical execution plan. Different physical implementations of logical operators have different time complexity, resource consumption and physical properties. In this process, the optimizer determines the cost of different physical implementations based on the statistics of the data, and selects the physical execution plan with the smallest overall cost.

Understand the Query Execution Plan has introduced some physical operators. This chapter focuses on the following aspects:

  • In Index Selection, you will learn how to select the optimal index to access tables when TiDB has multiple indexes on a table.
  • In Introduction to Statistics, you will learn what statistics TiDB collects to obtain the data distribution of a table.
  • Wrong Index Solution introduces how to use the right index when you find the index is selected wrongly.
  • Distinct Optimization introduces an optimization related to the DISTINCT keyword during physical optimization. In this section, you will learn its advantages and disadvantages and how to use it.
Was this page helpful?