| Bug #23666 | strange Innodb_row_lock_time_% values in show status; also millisecs wrong | ||
|---|---|---|---|
| Submitted: | 26 Oct 2006 14:24 | Modified: | 20 Jun 2010 1:13 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | mysql-noinstall-5.0.21-winx64 | OS: | Windows (win-x64) |
| Assigned to: | Sunny Bains | CPU Architecture: | Any |
| Tags: | innodb, innodb_row_lock_time, Innodb_row_lock_time_avg, Innodb_row_lock_time_max, STATUS | ||
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 Oct 2006 14:25]
Shane Bester
