You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug#21021670 - MISLEADING WARNING WHEN PER-QUERY STATEMENT TIME IS EXCEEDED
Issue here is, error reported on exceeding statement time contains
session variable "max_statement_time" in it. This error message
is misleading when max_statement_time is *not* set and timeout
value is set at statement level.
The timeout value can be set either at session level using
max_statement_time variable or at statement level. If execution
of statement takes more than timeout value then following
error is reported,
"Query execution was interrupted, max_statement_time
exceeded".
When session variable max_statement_time is not set and timeout
value is set at statement level then error message with
max_statement_time in it on timeout is misleading.
Fix:
Modified error message so that max_statement_time is not used
in it. Now on error following error message is reported,
"Query execution was interrupted, maximum statement execution time
exceeded"
eng "CHANGE MASTER TO with a MASTER_LOG_FILE clause but no MASTER_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file."
7144
7144
7145
7145
ER_QUERY_TIMEOUT
7146
-
eng "Query execution was interrupted, max_statement_time exceeded"
7146
+
eng "Query execution was interrupted, maximum statement execution time exceeded"
7147
7147
7148
7148
ER_NON_RO_SELECT_DISABLE_TIMER
7149
7149
eng "Select is not a read only statement, disabling timer"
0 commit comments