Re: sqlite locking and svn client concurrency

Johan Corveleyn <jcorvel_at_gmail.com> writes:

> If this is hard to handle in practice, and a long running
> multi-threaded client has to wait anyway for an entire write operation
> to be finished, I'm wondering if it would be much easier for such
> clients to also always use the "exclusive locking" mode. It would make
> most operations faster, and they have to wait anyway, so ... what
> would be the added value of still using non-exclusive mode?

Exclusive mode can be tricky to use as it is very easy to attempt to
open the database twice inadvertently, see r1336442 for example (that's
libsvn_client but a client could do something similar). It's also hard
for a client to release the exclusive lock as we don't provide a
suitable API; at present the client has to clear a pool to destroy the
context.

-- 
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download