Bug #76916 Option for max_statement_time is missing

• Submitted: 3 May 2015 9:18
• Modified: 11 May 2015 19:37
• Reporter: Daniël van Eeden (OCA)
• Status: Closed
• Category: MySQL Server: Options
• Severity: S3 (Non-critical)
• Version: 5.7.7-rc
• OS: Any
• CPU Architecture: Any

[3 May 2015 9:18] Daniël van Eeden

Description:
Documentation: https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_max_statement_...

According to the documentation there should be a --max_statement_time=# option. But it doesn't seem to be present in 5.7.7-rc. 

How to repeat:
The option is not advertised by mysqld:
$ mysqld --help --verbose | egrep 'max.statement.time'
$

And when present in the my.cnf the server aborts on startup.
2015-05-03T09:09:50.509496Z 0 [ERROR] unknown variable 'max_statement_time=1'
2015-05-03T09:09:50.509576Z 0 [ERROR] Aborting

However there is a global variables present:
mysql> select @@global.max_statement_time;
+-----------------------------+
| @@global.max_statement_time |
+-----------------------------+
|                           0 |
+-----------------------------+
1 row in set (0.00 sec)

mysql> set global max_statement_time=1;
Query OK, 0 rows affected (0.00 sec)

Suggested fix:
Make sure max_statement_time can be set in my.cnf

[3 May 2015 10:36] MySQL Verification Team

I think this is a valid request. Seems like an omission to have not it settable in my.cnf or server startup.

[11 May 2015 16:06] Paul DuBois

Noted in 5.7.8, 5.8.0 changelogs.

It was not possible to set the max_statment_time system variable at
server startup.

[11 May 2015 19:37] Daniël van Eeden

There is an e missing in the variable name.