I just committed a bunch of changes to deal with VACUUM. As it's an
expensive task which can block the database for quite a while I don't
just want to run it on every scan for every file involved. Here's the
compromise I've decided to use:
- library.db will be VACUUMed after all the tables have been emptied.
This usually should be really quick, as at that state the database is
mostly empty. It allows the db to start in a clean state.
- persist.db is never wiped. Therefore it's not always VACUUMed, but
only when fragmentation has reached a certain level (currently 20%).
Erland - I hope this works ok with your plugins. It should be
transparent, as it happens during the wipe task. But let me know if you
encounter any issue.
Now to the next big question: how to determine the best buffer size?...
--
Michael
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
