| Bug #52111 | 32-bit wraparound on buf_pool->ulint_clock causes high read ahead random | ||
|---|---|---|---|
| Submitted: | 16 Mar 2010 18:47 | Modified: | 2 Apr 2010 7:54 |
| Reporter: | Harrison Fisk | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.0,5.1 built-in | OS: | Any |
| Assigned to: | Marko Mäkelä | CPU Architecture: | Any |
| Tags: | innodb, read ahead, read ahead random, ulint_clock | ||
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
