http://bugzilla.spamassassin.org/show_bug.cgi?id=3471
------- Additional Comments From [EMAIL PROTECTED] 2004-06-04 17:16 ------- Subject: Re: add sanity check so too many tokens don't get expired On Fri, Jun 04, 2004 at 04:38:11PM -0700, [EMAIL PROTECTED] wrote: > Actually, it does. It determines the optimal atime to expiration and > then deletes everything < that. If this is a problem for DBM, then it > could happen for SQL as well, but slightly harder to recover from. Ah. I saw the "delete ... < ..." bit, and got confused (it was a very long night last night...) I guess the way to guard for this in SQL is to do a "select count(??) ..." before the delete, and see how many tokens will be removed. If too many, abort. If not, do the delete call. It adds more overhead, but ... At least for the delete, the appropriate rows would be in cache. :) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
