Andrew Donkin wrote:
So I tried to convert bayes_token to InnoDB to take advantage of its
row-level locking (this is advised by the developers but not reflected
in bayes_mysql.sql). After MySQL worked on that for a few days I
stopped it, dropped the database (innodb was very confused), and
Hi, people. This started as a plea for help but ended as a report of
an investigation, so hopefully it will be a useful addition to the
archives.
About 1% of my scans were taking more than 300 seconds. Extra
debugging in spamd showed me that the Bayes checks were the culprit:
13:38:05
