[EMAIL PROTECTED] wrote: > I can't make "OPTIMIZE TABLE dbmail_messageblks" because of more than 55Gb > data in it's table.
I would guess that is a generic problem for people running volatile sql databases. Doesn postgres' autovacuum solve this? > 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 ? It's not a dbmail issue perse. > > 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. You can do that already. Run dbmail-2.1 in cli mode though a tunnel: ssh [EMAIL PROTECTED] 'dbmail-imapd -n -f ~/dbmail.conf' that way you can give each user his/her own dbmail database, use different databases per user, or per group of users, use different sql drivers, different auth drivers, etc.... -- ________________________________________________________________ Paul Stevens mailto:[EMAIL PROTECTED] NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] The Netherlands________________________________http://www.nfg.nl
