# `VERSION::7.1.0` Binding a Query to a Historical Execution Plan Directly
+ Fix the execution plan of the SQL statement to a previously generated plan
+ Turn on **`tidb_enable_stmt_summary`** system variable to enable the feature
+ Useful for scenarios where the execution plan isn't fully constrained by the complete set of hints
  + Query involves TiFlash 
  + Join with three or more tables
  + Query that one or more subquery 
------------------------------------------------------------------------------
To fix the execution plan of an SQL statement to a historical execution plan, you can use `plan_digest` to bind that historical execution plan to the SQL statement. This approach is more convenient than binding based on the SQL statement itself.

During runtime, if the SQL executor comes across a hinted SQL query and the resulting execution plan does not align with the hint's expectations, a warning will be issued.