On Fri, Oct 28, 2011 at 7:26 AM, Stephan Beal <[email protected]> wrote:
> Hi, all, > > Occasionally (maybe once every two weeks or so) i'm seeing the following > when pulling/pushing the main fossil repo: > > [stephan@cheyenne:~/cvs/fossil/fossil-json]$ f up > Autosync: http://[email protected] > ... > Sent: 1634 33 0 0 > Error: Database error: database is locked > DELETE FROM unclustered WHERE rid IN (SELECT rid FROM private) > > Has anyone out there got an explanation (or theory!) for what might be > causing this? > > The offending SQL seems to be from here: http://www.fossil-scm.org/fossil/artifact/4631dc5d0c0?ln=642-646 The statement appears to be purely defensive, so I'm guessing we could take it out . But it would also be good to understand what is going on. When you do the auto-sync, are you doing it from an account that is read-only ("anonymous")? Maybe we are opening the database in read-only mode for a pull and hence this attempt to clean up a table in the database is failing - just a guess. -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
