On 11 August 2015 at 06:22, Simon Slavin <slavins at bigfraud.org> wrote:
> If you did set a timeout then SQLite wais a very short time (a millisecond > ?) before it tries again, then it waits a little longer, then a little > longer still, etc.. It gradually increases the time until the total time > reaches the time you set. It does not use the number you used as a guide > for the short times is waits. > If you're building sqlite yourself, note that this backoff behaviour is dependent on a specific preprocessor macro, HAVE_USLEEP. If not set, sqlite's busy handler sleeps in _one second_ intervals, which is not ideal for concurrent usage scenarios. (The above only applies to non-windows platforms. On windows the incremental backoff is always used.) -Rowan