Daniel Mejia wrote: > > Paul J Stevens wrote: >> So with 2000 users you have 2 to 3TB storage allocated already? >> > > There is a 3TB of storage, with 800Gb used. > > > >> So don't run dbmail-util -ay on a 800GB database! >> ... >> That is the header check (-b). You can safely skip that one, until you >> decide to rebuild the header cache tables. >> > > Rebuild header cache tables = ALTER TABLE ?
You won't rebuild header caches, unless you want/need to change you database's encoding, or have changed it in the past. If you do, you'll want to drop/create all the header cache tables: (dbmail_headername, dbmail_headervalue, dbmail_subjectfield, dbmail_datefield, dbmail_referencesfield, dbmail_fromfield, dbmail_tofield, dbmail_replytofield, dbmail_ccfield). But the queries that check the consistency and completeness of the headercaches may be long running, keeping a read-lock on those tables along the way. So for that reason alone, you will want to avoid them if at all possible. Same goes for some of the other queries run by the maintenance code. If it takes a long time to run them, but they don't normally find anything to fix, consider running them less often, if ever. The only queries you will probably want to run daily are -p and -d to queue messages for deletion that are flagged as such. To actually cleanout the messageblks involved in deleted messages you'll also want to add -t. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
