> Table "dbmail_messageblks" has almost 24Gb size (we have about 45000 > emails each day!). So when "OPTIMIZE TABLE dbmail_messageblks" starts > Mysql sets locking on this table and write operations delays while > optimize process runnig. > It has a very long time to parse 25Gb of data (MySQL creates temporary > files of the same size to rebuild table) and all clients who fetch > mail with pop3 or imap get time out error. In this state our MX server > (that push mail in MySQL server through dbmail-smtp utility) increases > number of processes in many times... > > If anybody now how to do optimize MySQL tables in such hard terms > - please answer.
It's a shame you can't run a mysql slave in two-way replication to handle the pop3/imap in a read/write state then any select/update are then later replicated back to the master. You still wouldn't receive any new email, but would allow users to access existing and move messages around within imap. S
