svn commit: r1454502 - /subversion/site/publish/docs/release-notes/1.8.html

[ph...@apache.org]

Author: philip
Date: Fri Mar  8 19:20:24 2013
New Revision: 1454502

URL: http://svn.apache.org/r1454502
Log:
* site/docs/release-notes/1.8.html
  (#exclusivelocking): Add exclusive SQLite locking of working copies.

Modified:
    subversion/site/publish/docs/release-notes/1.8.html

Modified: subversion/site/publish/docs/release-notes/1.8.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.8.html?rev=1454502&r1=1454501&r2=1454502&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.8.html (original)
+++ subversion/site/publish/docs/release-notes/1.8.html Fri Mar  8 19:20:24 2013
@@ -1944,6 +1944,40 @@ SVNMasterVersion 1.7.7
 
 </div>  <!-- svnmasterversion -->
 
+<div class="h3" id="exclusivelocking">
+<h3>Exclusive SQLite locking of working copies
+  <a class="sectionlink" href="#exclusivelocking"
+    title="Link to this section">&para;</a>
+</h3>
+
+<p>In the root of every Subversion working copy there is an
+<a href="http://sqlite.org" >SQLite</a> database in the <tt>.svn</tt>
+directory and Subversion clients use this database when accessing the
+working copy.  By default Subversion uses shared SQLite locking and
+this allows simultaneous access to the working copy by multiple
+clients with exclusive locks only being held for short periods.  The
+1.8 command line client can be configured to use exclusive SQLite
+locking by setting the following in the <tt>.subversion/config</tt>
+file:</p>
+<pre>
+[working-copy]
+exclusive-locking-clients = svn
+</pre>
+
+<p>or by using the command line option <tt>--config-option config:working-copy:exclusive-locking-clients=svn</tt>.
+
+<p>This reduces the locking overhead but does mean that only one
+Subversion client will be able to access the working copy at a time. A
+second client attempting to access a locked working copy will block
+for 10 seconds and then get an error. In most cases shared locking is
+preferred but if the working copy is on a network disk rather than a
+local disk the locking overhead is more significant.  When dealing
+with large working copies on network disks exclusive locking may give
+a significant performance gain, two or three times faster in some
+cases.</p>
+
+</div>  <!-- exclusivelocking -->
+
 </div>  <!-- enhancements -->
 
 <div class="h2" id="svn-1.6-deprecation">