RE: Any FSFS rep-sharing experts out there?
From: Bert Huijben <rhuijben_at_sharpsvn.net>
Date: Mon, 5 Oct 2009 15:18:34 +0200
> -----Original Message-----
Normally SQLite doesn't block the entire database, but just the tables it will be writing to when committing the current transaction.
The documentation also says something about: If the changes are too large to fit in the memory cache, the lock is promoted to a full exclusive lock to allow spilling intermediate results to the database file.
This last thing might be the case here....?
> Are we using these features of SQLite?
I don't think we install a busy handler, and I don't know if we want to enable this globally; probably not.
In the WC-Layer I would prefer an immediate negative answer over a delay..
Retrying is in most cases not a valid answer to this. Just look at the WIN32 retry loop, which is/was sometimes used on multiple levels.. which could make directory deletes take a half minute when there was a locked file where the code assumed a directory.
But maybe we should enable this for this specific repository use of SQLite.
Bert
>
------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.