Stefan Sperling wrote on Tue, Aug 02, 2011 at 10:22:23 +0200: > On Tue, Aug 02, 2011 at 10:09:06AM +0200, Markus Schaber wrote: > > > <Bert> stsp: (re: users@) read only operations on a fsfs repository > > don't > > > obtain a lock (and don't need write access). Only commit and revprop > > > changes should need write access. (I don't know what is required for > > bdb). > > > We don't use read locks, except for the sqlite (and maybe bdb) builtin > > > ones. > > > <danielsh> stsp: and packing > >
The short answer is "read-only access doesn't require a writeable mount". The revprop packing feature /of Subversion 1.8/ will continue to maintain this invariant. (The 1.7-dev incarnation of the feature didn't, but it has been removed and won't be released.) > > But AFAIR, V1.7 uses sqlite in the repository. Does that change > > anything? > > The sqlite db is used for the revprop packing feature. s/revprop packing/rep-sharing/ > This feature is only used at commit time. You cannot commit to a > read-only repository anyway :) > To clarify: the rep-sharing SQLite DB is only accessed during commits. Though, there is a standing backport for svn_fs_verify() which would break that... I'll follow up on dev@. > Subversion 1.6 uses sqlite for this, too, not just 1.7.