| Bug #21487 | Handle Leak on mysqld-nt.exe when using query cache | ||
|---|---|---|---|
| Submitted: | 7 Aug 2006 18:15 | Modified: | 22 Sep 2006 9:23 |
| Reporter: | Roland Volkmann | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 5.0.24,4.1.21,4.0.26 | OS: | Windows (windows) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Event, Handle, Leak, query cache, Semaphore | ||
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
[8 Aug 2006 15:44]
Roland Volkmann
[10 Aug 2006 21:16]
Roland Volkmann
Status of INNODB Engine 5.0.24
Attachment: Innodb_5024.TXT (text/plain), 15.97 KiB.
[12 Sep 2006 12:07]
Shane Bester
run "mysqld-nt.exe --query_cache_size=64M --query_cache_type" and it opened > 69000 handles on 5.0.24a
Attachment: bug21487_testcase.php (application/octet-stream, text), 920 bytes.
