aboutsummaryrefslogtreecommitdiff
path: root/Messages
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-02-18 15:54:24 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-02-18 15:54:24 -0400
commitd8125c9ea6d00b41f994162a0060f39e56107b12 (patch)
tree3f52039b7be3f4a52a124eb31cdbe341fcc4270f /Messages
parentd3012ca604d631122f3e304adbb5e60d5d706f82 (diff)
use WAL mode to ensure read from db always works, even when it's being written to
Also, moved the database to a subdir, as there are multiple files. This seems to work well with concurrent fscks, although they still do redundant work due to the commit granularity. Occasionally two writes will conflict, and one is then deferred and happens later. Except, with 3 concurrent fscks, I got failures: git-annex: user error (SQLite3 returned ErrorBusy while attempting to perform prepare "SELECT \"fscked\".\"key\"\nFROM \"fscked\"\nWHERE \"fscked\".\"key\" = ?\n": database is locked) Argh!!!
Diffstat (limited to 'Messages')
0 files changed, 0 insertions, 0 deletions