Skip to content

Consider using busy_timeout pragma on SQLite backend #15384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
udf2457 opened this issue Apr 1, 2025 · 0 comments
Open

Consider using busy_timeout pragma on SQLite backend #15384

udf2457 opened this issue Apr 1, 2025 · 0 comments
Labels
Milestone

Comments

@udf2457
Copy link

udf2457 commented Apr 1, 2025

Consider using the busy_timeout pragma when interacting with the SQLite backend (or at least exposing a config option).

The reason is that SQLite replication tools such as Litestream can, by definition, encounter race conditions if an application is attempting to write at the same time.

The recommended solution is to use the busy_timeout pragma

@udf2457 udf2457 changed the title Consider using busy_timeout on SQLite backend Consider using busy_timeout pragma on SQLite backend Apr 1, 2025
@rgacogne rgacogne added the auth label Apr 2, 2025
@Habbie Habbie added this to the auth-5 milestone Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants