←back to thread

SQLite concurrency and why you should care about it

(jellyfin.org)
369 points HunOL | 1 comments | 01 Nov 25 12:59 UTC | HN request time: 0.203s | 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. andersmurphy ◴[02 Nov 25 09:03 UTC] No.45788886[source]▶
Sqlite is fine you need to read the extensive documentation though to get the most out of it. It also has terrible defaults.

I think the author od this article missed sqlite_busy.

Once you do have it set up correctly, are handling a single writer at the application level and have litestream set up your off to the races assuming your app can scale on a single box (it most likely can).