3 ms·
No, it's indeed a very real problem. I ran into with a very small service.
by gwervc 2y ago
No, it's indeed a very real problem. I ran into with a very small service.
- liontwist 2y agoYou want to configure it so it has a timeout. Take turns. That’s how locks work. The only difference between SQLite and Postgres write locking is the granularity.
- miunau 2y agoIt's not a trivial difference like you suggest.
- liontwist 2y agoI agree It’s not a trivial difference in implementation and the concurrent write performance is probably a lot worse. But it’s talked about as if it’s a categorical limitation, the app will fail if there is concurrency. But it’s just a question of how much time will be spent locking. A website with a 16 process pool for handling requests will be fine.
- immibis 2y agosqlite also polls for lock availability