Re: Problems with INNODB in MySQL 4.0.6-gamma
On Tue, 4 Feb 2003, Kees Hoekzema wrote: I had the same problem, it went on until I had 44G of InnoDB space, with only 4G free. After getting tired of having to increase the number of files every week, I decided to dump all data with mysqldump, remove the files+ logs and recreate them. After that there was more than 24G free, and the database was a bit faster too :) (it took me more than 12 hours to dump restore, but it was worth the effort). In your case I think you should do the same only if you are running out of space every week or something. I too noticed that innodb won't give up it space, so this was the only solution that came to my mind, maybe there is a better way, but i haven't seen any tools to defragment an innodb database. What if making this procedure one database or table at a time, will it bring the effect, or does the _whole_ database file need to be recreated? Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)118-3322, 118-3115(fax) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Problems with INNODB in MySQL 4.0.6-gamma
Kees Hoekzema wrote: Hello, On Tuesday 04 February 2003 14:46, Grover Cussi N. wrote: restore to the original size ?, I see that the tendence of the innodb tables is to grow, and grow, and never will reduce the size, it is posible to control this? I had the same problem, it went on until I had 44G of InnoDB space, with only 4G free. After getting tired of having to increase the number of files every week, I decided to dump all data with mysqldump, remove the files+ logs and recreate them. After that there was more than 24G free, and the database was a bit faster too :) (it took me more than 12 hours to dump restore, but it was worth the effort). In your case I think you should do the same only if you are running out of space every week or something. I too noticed that innodb won't give up it space, so this was the only solution that came to my mind, maybe there is a better way, but i haven't seen any tools to defragment an innodb database. Had the same problem. Endded up deleting the logs every night using a cron-script. :-) - Cs. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Problems with INNODB in MySQL 4.0.6-gamma
Hello, On Tuesday 04 February 2003 14:46, Grover Cussi N. wrote: restore to the original size ?, I see that the tendence of the innodb tables is to grow, and grow, and never will reduce the size, it is posible to control this? I had the same problem, it went on until I had 44G of InnoDB space, with only 4G free. After getting tired of having to increase the number of files every week, I decided to dump all data with mysqldump, remove the files+ logs and recreate them. After that there was more than 24G free, and the database was a bit faster too :) (it took me more than 12 hours to dump restore, but it was worth the effort). In your case I think you should do the same only if you are running out of space every week or something. I too noticed that innodb won't give up it space, so this was the only solution that came to my mind, maybe there is a better way, but i haven't seen any tools to defragment an innodb database. Grover Cussi - kees mysql, query - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
