HI both of you, On Di, 30 Jun 2009, Helmut Grohne wrote: > Deleting 500 messages makes mu-index take about half an hour. Most of
from the issue where Stefano posted: > 2) I haven't straced it yet, but I read the corresponding source code. > Apparently > you're first extracting all indexed messages from sqlite and then, one by > one, you're > removing them with a) a DELETE query and b) a Xapian update. I don't know for > Xapian > (never programmed with its API), but for Sqlite doing a single DELETE query > with all > involved messages can be sensibly faster. If there is something similar for > Xapian, > doing a massive remove instead of several single removals might be the key. I added some debug statements to the source code and it seems that this is the reason. So I want to work on a patch that merges the deletes into one. Only one question, if one of you has some experience with sql (as I don't). How does one specify a LIST of ids to be removed in a single sql statement? Or can we just collect severat sql statements and execute them in one go? Best wishes Norbert ------------------------------------------------------------------------------- Dr. Norbert Preining Associate Professor JAIST Japan Advanced Institute of Science and Technology [email protected] Vienna University of Technology [email protected] Debian Developer (Debian TeX Task Force) [email protected] gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------------- DORCHESTER (n.) A throaty cough by someone else so timed as to obscure the crucial part of the rather amusing remark you've just made. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
