On 14 Jan 2019, at 18:54, Simon Slavin <[email protected]> wrote: > SQLite's own busy_timeout routine (the one you get if you don't supply your > own) uses exponential backoff. It first sleeps for a very small amount of > time, then checks the lock. If access is still prevented it sleeps longer, > then checks again. Then longer still, then longer still, until the amount of > time /since the routine started/ exceeds the timeout you set.
Hmm, from my attempt at interpreting the source code I gained the impression that the handler used exponential backoff for the first few attempts, but then used a constant period for the rest (up to the set limit). Is this not the case? -- Cheers -- Tim _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
