Bug #15748 Enable a way to shrink innodb file (ibdata) after drop database commands

• Submitted: 14 Dec 2005 16:49
• Modified: 13 May 2010 16:04
• Reporter: Bob McGuire
• Status: Open
• Category: MySQL Server: InnoDB storage engine
• Severity: S4 (Feature request)
• Version: 4.1 > or any
• OS: Linux (linux (or all))
• Assigned to: Assigned Account
• CPU Architecture: Any

[14 Dec 2005 16:49] Bob McGuire

Description:
There should be an easy way to reclaim space from an innodb database when dropping tables and/or databases.  I realize that that can be done by using innodb_file_per_table, but on servers without that option, the only way to accomplish this is to backup, rebuild and restore a database.

If you need more info, feel free to contact me.

Thanks, Bob

How to repeat:
n/a

Suggested fix:
see above description

[14 Dec 2005 16:53] Aleksey Kishkin

it's not a bug but rather feature request. I am changing severity to S4

[14 Dec 2005 16:56] Bob McGuire

Correct, my mistake.  This should have been logged as a feature request.

[20 May 2007 16:58] Curt Safranek

What is the status on this feature request from 2005?

[21 May 2007 13:03] Heikki Tuuri

No progress in this. I recommend using the innodb_file_per_table_feature.
--Heikki

[7 Feb 2008 19:39] Dmitry Arnautov

Any status updates on this ?

[17 Apr 2008 7:42] Todd Nine

I completely agree.  I definitely need to do this.  I'm working with MySQL as the back end on a high throughput JMS system.  Sometimes the consumers are down during upgrades, and our database size grows considerably.  Once all the messages have been consumed, I need a way to re-claim the unused space in the innodb files.