This is false.
When using innodb_file_per_table optimize table <table> gets mapped to alter table <table> type=InnoDB and the later command will issue a create from select that will result in a totally clean table, optimized and will free al the unused space. Try it by yourself, I can assure you it works: I just shrinked a 3GB .idb file to 500MB with this trick. Furthermore, in the unlucky case you didnt use the innodb_file_per_table at first (you unlucky!) you can enable it and then later issue an alter table <table> type=InnoDB. It will result in a new .idb file with just that table inside. From that moment on the optimize table trick will perfectly work. Later on when youll have done the alter table on every table to take them all out of the single innodb tablespace/file (which wont decrease when tables will be getting out of it), you can just trash it and manually reclaim all your disk space. >From http://dev.mysql.com/doc/refman/5.0/en/optimize-table.html : For InnoDB tables, OPTIMIZE TABLE is mapped to ALTER TABLE, which rebuilds the table to update index statistics and free unused space in the clustered index. See also: http://dev.mysql.com/doc/refman/5.1/en/multiple-tablespaces.html _____ Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Curtis Maurand Inviato: martedì 31 luglio 2007 15.29 A: DBMail mailinglist Oggetto: Re: R: [Dbmail] Table dbmail_messages is full mysqloptimize against an innodb table will not reclaim disk space. if anything, you're innodb file will grow. In fact it can end up twice as large as when you started. its one of the drawbacks of innodb tables. if you want to reclaim diskspace change the table type to myisam, then run mysqloptimize against the innodb table then alter the table back to innodb. Curtis Andrea Brancatelli wrote: > I strongly suggest you to use the innodb_file_per_table and to run an > optimize table dbmail_messages (and not only, also the others) from time > to > time to free some disk space. > > ciaociao > > -----Messaggio originale----- > Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto > di Sascha Braun > Inviato: martedì 31 luglio 2007 15.10 > A: DBMail mailinglist > Oggetto: Re: [Dbmail] Table dbmail_messages is full > > Is that the value you where asking for? > > innodb_data_file_path = ibdata1:10M:autoextend:max:128M > > I am now changing the max value, I hope i recognized everything > correctly. > > Best Regards, > > Sascha Braun > > Am Dienstag, den 31.07.2007, 16:30 +0400 schrieb alexander benaguev: >> give us "my.cnf", please >> >> alexander >> _______________________________________________ >> DBmail mailing list >> [email protected] >> https://mailman.fastxs.nl/mailman/listinfo/dbmail > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- Curtis Maurand Head Honcho Xyonet Hosting Services Biddeford, ME 04005 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
