Expand SQLite comment to talk about busy_timeout#913
Merged
Conversation
Another small one. While writing documentation for SQLite tonight I tried using `busy_timeout` as an alternative to setting a maximum of one active connection. It kind of works, but I found overall that I'd still get `SQLITE_BUSY` errors with `busy_timeout` once iterating the test suite at higher counts like `-count 100`. Overall, I think the single active connection is still the way to go. Here, add a note on that so I won't forget about this in the future.
bgentry
approved these changes
May 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Another small one. While writing documentation for SQLite tonight I
tried using
busy_timeoutas an alternative to setting a maximum of oneactive connection. It kind of works, but I found overall that I'd still
get
SQLITE_BUSYerrors withbusy_timeoutonce iterating the testsuite at higher counts like
-count 100.Overall, I think the single active connection is still the way to go.
Here, add a note on that so I won't forget about this in the future.