On Tue, 2010-11-02 at 08:40 +0000, RW wrote: > On Tue, 02 Nov 2010 01:02:48 +0000 > Martin Gregorie <mar...@gregorie.org> wrote: > > > On Mon, 2010-11-01 at 23:05 +0000, RW wrote: > > > On Mon, 01 Nov 2010 22:09:03 +0000 > > > Martin Gregorie <mar...@gregorie.org> wrote: > > > > > > > On Mon, 2010-11-01 at 21:15 +0000, RW wrote: > > > > > I don't think it's a matter of locking-out updates - presumably > > > > > token updates that occur after the start of a sync should go > > > > > into the new journal file. > > > > > > > > > It may easily be a locking problem: To quote from the MySQL > > > > manual: > > > > > > > > > SQL backends don't use journalling. > > > > > But you're still using a batch operation to play the journal file into > > the database and, if the OP isn't using InnoDB its going to hold a > > table lock while it runs. That's going to block SA queries unless > > (ugh!) MySQL defaults to allowing dirty reads. > > The OP isn't using SQL, and AFAIK SA doesn't use a journal file with > SQL.
I thought he said he was using a MySQL Bayes database. OK, I'll shut up now. Martin
