Joey Hess e006acef22 avoid reposize database locking overhead when not needed ... Only when the preferred content expression being matched uses balanced preferred content is this overhead needed. It might be possible to eliminate the locking entirely. Eg, check the live changes before and after the action and re-run if they are not stable. For now, this is good enough, it avoids existing preferred content getting slow. If balanced preferred content turns out to be too slow to check, that could be tried later.		2024-08-28 10:52:34 -04:00
..
Wanted.hs	avoid reposize database locking overhead when not needed	2024-08-28 10:52:34 -04:00