Skip to content

docs(server): synchronous defaults to NORMAL in WAL mode #21

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

Merged
everpcpc merged 1 commit into from
Oct 5, 2026
+3 −2
Merged

docs(server): synchronous defaults to NORMAL in WAL mode #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions src/content/docs/server/configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,8 @@ Every key below is commented out at its default value; uncomment to change it. A
# concurrent writes wait instead of failing. The task read pool defaults to 2
# connections — task work is serial per worker (TASK_POOL_SIZE defaults to 1);
# an explicit pool-size applies to the task pool too.
# [database.pragmas] # extra SQLite pragmas, TOML only
# synchronous = "NORMAL"
# [database.pragmas] # extra SQLite pragmas, TOML only. synchronous defaults to NORMAL in WAL mode, FULL otherwise
# synchronous = "FULL"
# cache_size = "-1820" # page cache per connection, negative = KiB; default: 16 MiB per database split between its connections (512..2048 KiB clamp)

[tasks-db]
Expand Down
1 change: 1 addition & 0 deletions src/content/docs/server/enhancements/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,5 +30,6 @@ Intentional differences from the Java behavior:
- `GET /actuator/sessions` without `?username=` lists all sessions (Java rejects it).
- `/api/v1/books/{bookId}/next` and `/previous` break `numberSort` ties by book id; Java's tie-handling is unstable — see [Next/previous navigation](/server/enhancements/next-previous).
- Memory is bounded regardless of CPU cores: 16 MiB SQLite page-cache budget per database (`cache_size` pragma overrides), and `malloc` arenas capped at 2 on Linux/glibc (`MALLOC_ARENA_MAX` overrides; `1` saves more on tiny boxes but serializes C-side allocation).
- `synchronous` defaults to `NORMAL` in WAL mode (Java: SQLite's `FULL`): commits no longer fsync, so write bursts (komf full-library match, scans) don't saturate the disk; a power loss can roll back the last committed transactions but cannot corrupt the database. `[database.pragmas] synchronous = "FULL"` restores Java behavior.
- SQL statements that run 500 ms or longer are logged at WARN with their text (log target `komga_db::slow_query`); lock waits count toward the time, so lock-starved writers show up too. The Java version has no slow-query log.
- Collection/read list covers: adaptive collage of up to 4 member covers (1 full, 2 side-by-side, 3 = 1 tall + 2 stacked, 4 = 2×2) on a blurred, dimmed blowup of the first cover (neutral gray when no cover is available); Java renders a fixed 2×2 grid on black, cycling members.
Loading