bert hubert 🇺🇦🇪🇺🇺🇦The worldly news is dragging me down. And I may also have found a bug in sqlite3. sqlite3 is one of these things I rely on absolutely, a sane quality project. so this is doubly depressing.
Sami Lehtinen@bert_hubert More details about the #SQLite3 plz!
@sl sqlite3_rsync appears to be delivering corrupt databases.. sometimes. Very hard to debug.
synlogic4242@bert_hubert @sl it has a perfect storm of challenges: concurrency, network and ACID to arbitrary filesystem backends. I have a TODO to take a hard look at how Litestream manages it. since doing replication across network is approx the same challenge as sqlite-rsync
@bert_hubert I wasn’t previously aware of sqlite3_rsync, but it certainly seems well-suited for updating read-only mirrors of a master database. It is a highly practical model for specific use cases.
After reading up on its intended functionality, I can see that it operates in a complex space of engineering trade-offs. Guaranteeing reliability is straightforward if you simply enforce a global read/write lock on the database, but that would severely degrade write performance. Improving performance beyond that baseline inherently introduces complexity and brittleness.