https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6444
--- Comment #14 from Mark Martinec <[email protected]> 2010-06-10 17:44:23 EDT --- > Yes, it does create the string on each for the update, but that is exactly > what it is meant to do. This is to avoid the deadlocks. So it does do the > update one by one. A statement handle can be prepared fully in advance, doing so should not have any effect on locking. Also updating the bayes_vars in each iteration is just a waste. It can be argued whether 'UPDATE bayes_token SET atime=...' for all tokens should be run as a single transaction (as in my patch), or as individual transactions (as your code does). I'm not sure about locking, but I can tell that the whole update ran much slower if done with one-transaction-per-token. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
