Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Suggest increasing busy_timeout to prevent errors #7945

Closed
wants to merge 2 commits into from
Closed

Suggest increasing busy_timeout to prevent errors #7945

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c55ee2
Suggest increasing busy_timeout to prevent errors
KnockOnWoodNode Sep 1, 2023
cd0cf08
docs: Suggest increasing busy_timeout to prevent errors
KnockOnWoodNode Sep 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/sqlite.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,9 +39,14 @@ journal_mode=wal
busy_timeout=5000 // Overried with the db.sqlite.busytimeout option.
```

Default `busy_timeout` unit is milliseconds.
A 5s timeout could lead to `SQLITE_BUSY` errors,
which can be prevented by setting a longer timeout.

The following pragma options are set by default but can be overridden using the
`db.sqlite.pragmaoptions` option:


```
synchronous=full
auto_vacuum=incremental
Expand All @@ -66,7 +71,7 @@ Example as follows:
[db]
db.backend=sqlite
db.sqlite.timeout=0
db.sqlite.busytimeout=10s
db.sqlite.busytimeout=1m
db.sqlite.pragmaoptions=temp_store=memory
db.sqlite.pragmaoptions=incremental_vacuum
```