Bug #59738 | update a timestamp variable every time reaches Max_used_connections | ||
---|---|---|---|
Submitted: | 26 Jan 2011 11:47 | Modified: | 11 Mar 2014 21:13 |
Reporter: | Jordi Prats (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Options | Severity: | S4 (Feature request) |
Version: | 5.1 and 5.5 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | Contribution, max_used_connections, MySQL, patch |
[26 Jan 2011 11:47]
Jordi Prats
[26 Jan 2011 11:52]
Jordi Prats
patch for that feature
Attachment: patch.mysql.51.max_used_connections_ts.patch (text/x-patch), 1.49 KiB.
[26 Jan 2011 12:15]
Valeriy Kravchuk
Thank you for the feature request and code contributed.
[29 Mar 2011 12:44]
Jordi Prats
Patch for MySQL 5.5.10
Attachment: patch.mysql.55.max_used_connections_ts.patch (text/x-patch), 1.95 KiB.
[29 Mar 2011 12:47]
Jordi Prats
Attached a new patch for MySQL 5.5
[12 Feb 2014 9:17]
Jordi Prats
same patch for mysql 5.1 (*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: patch.mysql.51.max_used_connections_ts.patch (text/x-patch), 1.49 KiB.
[12 Feb 2014 9:17]
Jordi Prats
same patch for mysql 5.5 (*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: patch.mysql.55.max_used_connections_ts.patch (text/x-patch), 1.95 KiB.
[11 Mar 2014 21:13]
Paul DuBois
Noted in 5.7.5 changelog. A new status variable, Max_used_connections_time, indicates the time at which Max_used_connections reached its current value. Thanks to Jordi Prats for the patch.