Strictly an InnoDB issue. Dan
On 11/16/06, Chaos Engine <[EMAIL PROTECTED]> wrote:
2006/11/15, Dan Buettner <[EMAIL PROTECTED]>: > It's normal for space to not be reclaimed from the InnoDB file, yes. > You could change your setup to use the 'innodb_file_per_table' option > to change the behavior; with that in effect, deletes/dropped tables > etc will lead to reclaimed space after optimizing. > > However, you'd also have to either drop your current data and > re-import, or switch to myisam and back again to get the data into > separate table files. Isn't there any easier solution to reclaim garbage space? This is somewhat silly to drop/reimport or convert tables to myisam and back again. Is it strickly innodb issue ? > Dan > > On 11/15/06, Curtis Maurand <[EMAIL PROTECTED]> wrote: > > I think this question has been asked, but I have not yet found an answer > > to the problem. > > > > I'm running MySQL 5.0.22 on Gentoo Linux AMD 64. Its blazingly fast, > > mostly. I'm running a package called dbmail on it. > > http://www.dbmail.org. All mail is stored in the database. After running > > a dbmail-util which deleted somewhere around 9,000 messages, I ran > > mysqloptimize against the database. After running mysqloptimize the > > innodb file (ibdata1) was larger than it was before i started. is this > > normal? If not, how do I change the behavior? > > > > I'm happy to forward any relevant data that you need. > > > > Thanks, > > Curtis > > > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: http://lists.mysql.com/mysql?unsub= [EMAIL PROTECTED] > > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- Chaos greets U
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
