On Fri, May 30, 2003 at 06:54:37PM -0500, Stewart, John wrote: > So this explains what happens if the DB gets too *small*. But what governs > how *big* the database can get? Would it just be big enough to contain the > last 500,000 seen tokens? Would this be a problem for performance/DB size?
Nothing really. 2.5x is based on "expire every X messages, down to min_db_size". You had a good point about the expiry... I forgot all about that age thing. So you could disable autoexpire by setting it really high, then when you do the manual force-expire, aim it at another prefs file that leaves the setting at the default 5000. Klugy, but that's all I can think of at the moment. 2.6x is based on "ok the db is too large, so do an expire now". Same with journal syncs. -- Randomly Generated Tagline: As usual, this being a 1.3.x release, I haven't even compiled this kernel yet. So if it works, you should be doubly impressed. (Linus Torvalds, announcing kernel 1.3.3 on the linux-kernel mailing list.)
pgp00000.pgp
Description: PGP signature
