Bug #76915 | Misleading warning when per-query statement time is exceeded | ||
---|---|---|---|
Submitted: | 3 May 2015 9:06 | Modified: | 7 May 2015 16:29 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Errors | Severity: | S3 (Non-critical) |
Version: | 5.7.7-rc | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | usability |
[3 May 2015 9:06]
Daniël van Eeden
[4 May 2015 16:42]
MySQL Verification Team
Hi Daniël, What do you think about this message instead: + eng "Query execution was interrupted, maximum statement execution time exceeded"
[5 May 2015 6:55]
Daniël van Eeden
@Shane That would be perfect.
[7 May 2015 16:29]
Paul DuBois
Noted in 5.7.8, 5.8.0 changelogs. The error message indicating that statement execution was interrupted referred to the max_statement_time system variable, even if the relevant timeout was a per-statement value. The error message is now more generic.