SQLite: when connecting to an in-memory database, limit to 1 concurrent connection #3255
Conversation
This file contains 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
…nt connection Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
berndverst
approved these changes
Dec 6, 2023
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.
By default the Go database/sql package opens multiple connections to a database.
However, when using SQLite with an in-memory database, this can cause conflicts if two transactions are executed at the same time.
When the SQLite database is stored on disk, the WAL allows multiple operations in parallel and keeps them pending for up to "busyTimeout". However when the database is in-memory, based on some real-world data, a transaction blocks the database and busyTimeout isn't respected.
Using a single connection makes it so Go never tries to create 2 transactions in parallel.