>From the InnoDB manual: Dropping a table or deleting all rows from it is guaranteed to release the space to other users, but remember that deleted rows can be physically removed only in a purge operation after they are no longer needed in transaction rollback or consistent read.
Perhaps that helps. Edward Dudlik Becoming Digital www.becomingdigital.com ----- Original Message ----- From: "I-A.Kotopoulos" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, 20 June, 2003 04:36 Subject: InnoDB file size... I am currently working on some experiments and have to deal with some millions of tuples. As you can imagine indexing is essentiall. However My InnoDB file has grown to over 3.6G and fragmentation is sometimes a big problem. Additionally the file keeps its size even after dropping the 'big' tables. So, any suggestions in order to optimize the space usage? thanx in advance aik_b -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
