Statement Timeout separately for SELECT and DML queries

Registered by Muhammad Irfan

mysql [localhost] {msandbox} ((none)) > show variables like 'max_statement%';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
| max_statement_time | 0 |
+--------------------+-------+
1 row in set (0.00 sec)

mysql [localhost] {msandbox} ((none)) > SET max_statement_time=1;
Query OK, 0 rows affected (0.00 sec)

mysql [localhost] {msandbox} ((none)) > select * from information_schema.tables;
ERROR 1883 (70101): Query execution was interrupted, max_statement_time exceeded

mysql [localhost] {msandbox} (test) > UPDATE Country SET Continent='Asia' WHERE Continent = 'Oceania';
ERROR 1883 (70101): Query execution was interrupted, max_statement_time exceeded

* it would be good to add an option to limit it to selects only.
* What happens if a statement is blocked by a global lock? will it be also killed?

Also, documentation is not clear about this.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Low
Drafter:
Muhammad Irfan
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.