https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7014
--- Comment #5 from peter gervai <g...@grin.hu> --- (In reply to AXB from comment #4) > sidenote: Redis Bayes backend would give you way less problems than SQL and > a huge performance advantage. (site wide bayes only) Indeed redis is interesting despite its several shortcomings, including a serious FD leak (Bug 7034) I had to play with this morning. Seems to be fixed now so doesn't die in every few hours. Still have to use SQL for AWL and probably I have to ditch redis when I move over per-user-configs (unless mr. author prefix the keys with userid and solve the problem, don't ask me why he haven't). This doesn't quite solve the original problem though: for a massively parallel updating code ignoring locking is a nonworking solution in the long run. Now redis saves me to SELECT FOR UPDATE'ing all the code to rowlock everything beforehand and release after, which ought to have been done. -- You are receiving this mail because: You are the assignee for the bug.
