Navidrome Daily: Database on the Mind
Two unrelated but database-focused efforts landed today: an experimental spike into running Navidrome on an embedded Postgres engine, and a bug fix that stops the backup restore command from silently wiping a database when the backup file is missing.
Duration: PT1M58S
Episode overview
This episode is a short developer briefing from Navidrome Daily.
It explains recent repository work in plain language.
- Show: Navidrome Daily
- Published: 2026-09-05T10:01:43Z
- Audio duration: PT1M58S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's September 5th, and today's activity puts the database layer front and center — one exploratory, one urgent.
The bigger story for reliability is PR 6085, from contributor Huang-404-Q. It fixes a serious edge case in the backup restore command. Right now, if you run a restore and point it at a backup file that doesn't actually exist — say, a path that's relative to the working directory instead of the configured backup path…
On the exploratory side, Deluan opened PR 6084, a spike testing whether Navidrome could run on an embedded PostgreSQL engine, using a WebAssembly runtime, the same way it already embeds the tag-reading library today. The idea: no external Postgres service, no C-go dependency, just a compiled database engine running…
Taken together, the theme is scrutiny of how Navidrome stores and moves its data — from making sure restores fail safely, to questioning what database engine sits underneath the application entirely.
What's next: watch for the restore fix to land and get backported, since it addresses real data-loss risk. The embedded Postgres spike is worth watching too, though it's early — if it goes anywhere, it would be a meaningful shift in how…
Th…