Let me see if I understand what you wrote. You are saying that whenever the index thread is woken up, this journal file is created and written to, regardless of whether there's actually anything left to index?
How about not starting a sqlite transaction *unless* there's something to index? I'd like to respectfully propose that it's buggy behavior for a process to be writing to disk when there's nothing to be done. ------------------------------------ On Sep 27, 2007, at 3:23 PM, jamie jamiemcc-at-blueyonder.co.uk wrote: wont work we are not constantly writing to it - we do start a transaction on the sqlite databases when the index thread is woken up (this creates the journal files) this should not cause any problems though as the transaction is closed when the index thread goes back to sleep and the journal dissapears even though nothing was written to the db it should not be a performance issue at all? jamie _______________________________________________ tracker-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/tracker-list
