←back to thread

SQLite concurrency and why you should care about it

(jellyfin.org)
353 points HunOL | 1 comments | 01 Nov 25 12:59 UTC | HN request time: 0s | source
Show context
mangecoeur ◴[01 Nov 25 15:14 UTC] No.45782293[source]▶
Sqlite is a great bit of technology but sometimes I read articles like this and think, maybe they should have used postgres. I you don’t specifically need the “one file portability” aspect of sqlite, or its not embedded (in which case you shouldn’t have concurrency issues), Postgres is easy to get running and solves these problems.
replies(11): >>45782439 #>>45782829 #>>45782906 #>>45782930 #>>45782932 #>>45783524 #>>45784757 #>>45784918 #>>45787275 #>>45788143 #>>45788886 #
1. heavyset_go ◴[02 Nov 25 06:05 UTC] No.45788143[source]▶
I run Jellyfin in a multi-arch cluster because I hate myself, and this would force me to think about where Jellyfin/Postgres is deployed because Postgres databases aren't portable.

I already had to do that for my authoritative PG deployment, and my media manager shouldn't require a full RDBMS.

Using SQLite for Jellyfin has made running it wherever really, really easy, same thing with doing backups and lazy black box debugging.