Bug #61030 Make an I_S table of client error codes
Submitted: 2 May 2011 19:37 Modified: 3 May 2011 6:29
Reporter: Baron Schwartz (Basic Quality Contributor) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Performance Schema Severity:S4 (Feature request)
Version: OS:Any
Assigned to: Marc ALFF CPU Architecture:Any
Tags: qc

[2 May 2011 19:37] Baron Schwartz
Description:
A lot of problems could be detected earlier in production by monitoring for error responses.  For example, an increase in lock wait timeouts, deadlocks, or aborted clients.  Can we get MySQL to maintain a counter per error and expose them via an I_S table or a P_S table?

How to repeat:
Feature request
[3 May 2011 6:29] Valeriy Kravchuk
Thank you for the feature request.