Hi all,
The updated MySQL migrations scripts are in CVS. All tables are now
prefixed by 'dbmail_'. They also remove some unwanted indexes.
I've tested the InnoDB script on our DBMail db, and all seems to work
OK. Can other people test the scripts as well?
There's a possibility that the
We only have about 5.5-6GB of actual data in our dbmail database,
but usage keeps growing over time, eventually filling the 18GB
available disk space. We ended up running periodic vacuum fulls
from cronjobs (twice a month lately), and that does drop the used
disk space down some, but it
Matthew T. O'Connor wrote:
Jesse Norell wrote:
Hello,
We've been dealing with this issue quite recently (even with some
assistance from Dan in #dbmail{,-dev} channels). The below
recommendations are right on par with what I've found for pgsql
maintenance (ie. sufficiently high
What happens when the disk fills up? Some systems are designed to grow
until they fill their bounds, and only then begin to recycle space
internally.
When the disk fills up, all havoc breaks loose. :) It does not recycle
space as you mentioned. If we can free some other space on the
