LP #1307432: [DOC] Clarify some points in using max_statement_time
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Activity
Done
Details
Assignee
UnassignedUnassignedReporter
lpjirasynclpjirasync(Deactivated)Time tracking
No time loggedComponents
Fix versions
Affects versions
Priority
LowParent
None
Details
Details
Assignee
Unassigned
UnassignedReporter
lpjirasyncTime tracking
No time logged
Components
Fix versions
Affects versions
Priority
LowParent
None
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created January 24, 2018 at 7:07 AM
Updated January 24, 2018 at 7:08 AM
Resolved January 24, 2018 at 7:08 AM
**Reported in Launchpad by Laurynas Biveinis last update 01-08-2017 06:50:29
[In:Percona Server Documentation]
http://www.percona.com/doc/percona-server/5.6/management/statement_timeout.html
We support timeouts for data-modifying statements too, differing from MySQL 5.7.4 implementation. Some of these statements might be unsafe for timeouts (e.g. DDL, and updates to non-transactional SEs?), others should be OK (updates to transactional SEs?). Document which is which, warn about using timeouts with unsafe-for-timeout statements. This might need research first.