Comment 3 for bug 1841634

“a lot of churn”? — please explain.

I believe the rpro mechanism does exactly what we need here (but I admit I was looking at the 3.15 version of the code, not 7.0). The scanOnce code is pretty simple and short so duplicating it won’t be hard, the only difference being that the queue processor checks pact and sets rpro (and putf perhaps?) if needs be. The word Force isn’t quite right for the API name though, I’ll keep thinking on that.

Why are you thinking we might have to introduce dbNotify here? Now /that/ would be churn.