Recently, the great Heikki said that the following directive should also defragment your InnoDB tables:
ALTER TABLE table_name TYPE=InnoDB; How was it put...ah yes, a "table no-op". Regards, Chris On Fri, 2003-09-19 at 01:32, Gustavo A. Baratto wrote: > from the manual: > --------- > 7.5.12.3 Defragmenting a Table > > If there are random insertions or deletions in the indexes of a table, > the indexes may become fragmented. By fragmentation we mean that the > physical ordering of the index pages on the disk is not close to the > alphabetical ordering of the records on the pages, or that there are > many unused pages in the 64-page blocks which were allocated to the index. > > It can speed up index scans if you periodically use mysqldump to dump > the table to a text file, drop the table, and reload it from the dump. > Another way to do the defragmenting is to ALTER the table type to MyISAM > and back to InnoDB again. Note that a MyISAM table must fit in a single > file on your operating system. > > If the insertions to and index are always ascending and records are > deleted only from the end, then the file space management algorithm of > InnoDB guarantees that fragmentation in the index will not occur. > -------- > > Franky wrote: > > Hi all, > > > > for myisam tables we have "optimize table" that can be cronned to run at > > night, but is there something like this for the innodb table type as well? > > > > > > Franky > > > > > > -- > -------------------------------------------------------------------------- > Gustavo Baratto - Systems Engineer > [EMAIL PROTECTED] * (604) 638-2525 ext. 408 > > Technical support web-site: http://support.superb.net > Superb Internet Corp. "Ahead of the Rest" > ------------------------------------------------------------------------- > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
