Austin Clements <amdra...@mit.edu> writes: > The trouble with this approach is that the OS doesn't have to flush > logfile to the disk platters in any particular order relative to the > updates to Xapian. So, after someone trips over your plug, you could > come back with Xapian saying you have 500 log entries when your > logfile comes back with only 20. The only way I know of to fix this > is to fsync after the logfile write, which would obviously have > performance issues. But maybe there are cleverer ways?
Sorry to jump in almost a year after the fact, but.. How bad do you think those performance issues are going to be? I don't see them as prohibitive, even in the case where you write a log entry for every message being tagged. Xapian's doing an fsync each time we commit, isn't it? (Or is there some cute trick where it rename()s the database?) If, instead of truncating, you replay logged operations, I think you can get away with just writing log entries for user-level operations (like "notmuch tag +mytag to:somequery") which could touch a lot of messages. This would then only require one fsync on the log file before doing a lot of tag updates. Ethan _______________________________________________ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
