Re: SQLite locking and FSFS rep-sharing

Philip Martin <philip.martin_at_wandisco.com> writes:

> The second commit doesn't wait for the 10 second SQLite busy timeout, it
> gives the 'database is locked' error immediately.
>
> Should we be doing more to support concurrent writes here? An explicit
> loop in the post-commit? A different SQLite configuration?

A change from 1.6 is that 1.7 uses sqlite for packed revprops. It turns
out that the packed revprop database doesn't have this problem because
access to it is protected by the FSFS repository lock.

We could change the rep-sharing database access to take the FSFS
repository lock. Read access to the database already occurs at a point
when the lock is held.

-- 
Philip