Bug #77461 Rename max_statement_time% variables to max_execution_time%
Submitted: 23 Jun 2015 19:37 Modified: 19 Jul 2015 17:07
Reporter: Gleb Shchepa Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Parser Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any

[23 Jun 2015 19:37] Gleb Shchepa
If we decide to implement the suggestion from bug#21306392 "REMOVE OLD-STYLE MAX_STATEMENT_TIME HINT (REPLACE WITH MAX_EXECUTION_TIME)", it would be nice to rename system variables/command line options from the max_statement_time% pattern to the max_execution_time% pattern:

* --max-statement-time --> --max-execution-time
* @@max_statement_time --> max_execution_time
* @@max_statement_time_exceeded --> @@max_execution_time_exceeded
* @@max_statement_timer_set --> @@max_execution_timer_set
* @@max_statement_time_set_failed --> @@max_execution_time_set_failed

How to repeat:
[19 Jul 2015 17:07] Paul DuBois
Noted in 5.7.8 changelog.

The max_statement_time system variable was renamed to
max_execution_time. The Max_statement_time_exceeded,
Max_statement_time_set, and Max_statement_time_set_failed status
variables were renamed to Max_execution_time_exceeded,
Max_execution_time_set, and Max_execution_time_set_failed.