| Bug #35077 | Very slow DROP TABLE (ALTER TABLE, OPTIMIZE TABLE) on compressed tables | ||
|---|---|---|---|
| Submitted: | 5 Mar 2008 12:13 | Modified: | 19 Jun 2010 0:25 |
| Reporter: | Philip Stoev | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB Plugin storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.1.42 | OS: | Any |
| Assigned to: | Marko Mäkelä | CPU Architecture: | Any |
| Tags: | buf_LRU_invalidate_tablespace | ||
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
[5 Mar 2008 12:27]
Philip Stoev
[22 Jan 2010 23:05]
Vojtech Kurka
gdb output
Attachment: gdb.txt (text/plain), 12.91 KiB.
[28 Jan 2010 13:25]
Mathias Walter
error log file during the three gstack traces
Attachment: mysql.err (application/octet-stream, text), 26.29 KiB.
[28 Jan 2010 13:26]
Mathias Walter
1st stack trace from 12:27 AM
Attachment: gstack_1.txt (text/plain), 10.47 KiB.
[28 Jan 2010 13:27]
Mathias Walter
2nd stack trace from 12:29 AM
Attachment: gstack_2.txt (text/plain), 11.55 KiB.
[28 Jan 2010 13:27]
Mathias Walter
3rd stack trace from 12:30 AM
Attachment: gstack_3.txt (text/plain), 15.19 KiB.
[28 Jan 2010 16:41]
Vojtech Kurka
mysqld error log with innodb status output
Attachment: mysqld_errlog.txt (text/plain), 38.34 KiB.
