On 11/29/07 7:45 PM, "Matt Kettler" <[EMAIL PROTECTED]> wrote:
> As a starting point I'd suggest: > either disable your force-expire calls or disable bayes_auto_expire. I am doing only force-expires. I disabled auto-expire when I started doing force expires. > Doesn't matter to me which, but you really want to be expiring at the > bayes_expiry_period interval > drop bayes_expiry_period to 3 hours, if you're still using > force-expires, make it just a tad under 3 hours. > expand bayes_expiry_max_db_size to at least 300,000, maybe 600,000. Thanks. I'll give this a try. If bayes_expiry_period is set to 3 hours, shouldn't the force-expire be just *over* 3 hours, not just under? Otherwise wouldn't the "can't use estimation method for expiry" always be triggered as it is now? I planned to have the PostgreSQL DB enabled on one live system tonight, but have to wait on a couple of missing RPM's to be installed. I have great hopes for it... I am running a nearly 2 billion record database under PostgreSQL with great performance. A few million records should be nothing... Guess it depends on what the update vs. read load is. I would think it would be extremely useful to be able to treat manually-learned rules separately from auto-learned rules. In a high volume environment, you'd want to keep manually learned rules far longer than you could possibly keep auto-learned ones. Manually learned rules should be more important. Wes
