My question adressed mainly to Paul J Stevens and other developers. But all 
other users are strongly welcome!

I run dbmail 2.0.7 on separate mysql server with innodb support and about 5K 
mailboxes on it.
Everything works rather fast, but some things are not clear for me:

I can't make "OPTIMIZE TABLE dbmail_messageblks" because of more than 55Gb data 
in it's table.
As far as I know nor mysql nor postgre can't do this procedure in "on-line 
mode" ( without locking tables).

So I would like to know about feature dbmail releases - shall this problem be 
solved or not ?

In my opinion it can be solved by a little bit another table structure. For an 
example we can make new
database for each user and than make table space for him from 
create-mysql-innodb file.

In this case we shall be able to run optimize for each user separately, because 
his dbmail_messageblks is
much less than dbmail_messageblks of all users on server!

As for dbmail_pop3, dbmail_imap, dbmail_smtp there won't be revolutionary code 
changing,
only first time sql server connection (we have to do not "use dbmail" command, 
but "use username" instead)


What do you think about this idea?


Reply via email to