RE: Efficient revprop access in lib_repos
From: Bert Huijben <bert_at_qqmail.nl>
Date: Mon, 12 Oct 2015 00:10:08 +0200
How does this affect multiple processes accessing the same repository?
This caching looks like a nice speedup in some common cases, but I’m wondering if we are adding new race conditions on revision property updates. We had to add specific atomic revprop change apis to resolve/limit some older race conditions and this looks at the surface like it might introduce a few new cases.
From: Stefan Fuhrmann [mailto:stefan.fuhrmann_at_wandisco.com]
[This is the rationale and additional documentation to an upcoming
set of commits.]
When changing a revprop, we provide the following visibility guarantees:
1. A request that ends before the set_revprop started, sees the old value (duh!).
This is an archived mail posted to the Subversion Dev mailing list.