| 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 | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[26 Jan 2011 11:52]
Jordi Prats
[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.
