[DOC] Clarify some points in using max_statement_time

Bug #1307432 reported by Laurynas Biveinis on 2014-04-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Invalid
Undecided
Unassigned
5.5
Invalid
Undecided
Unassigned
5.6
Triaged
Medium
Borys Belinsky
5.7
Invalid
Undecided
Unassigned

Bug Description

[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.

tags: added: max-statement-time

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3126

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers