News for hackers. Stuff that matters.
Re:Dqlite – High-Availability SQLite by tyingq on Friday August 30, 2019 @07:31AM (#20837570)
The very top of that page suggests WAL with PRAGMA synchronous = 0 accomplishes roughly the same objective.
Re:Dqlite – High-Availability SQLite by rockwotj on Friday August 30, 2019 @07:44AM (#20837617)
Based on the following header file, it would seem that they are using this unsupported module.

https://github.com/canonical/dqlite/blob/master/src/vfs.h

Re:Dqlite – High-Availability SQLite by cyphar on Friday August 30, 2019 @08:11AM (#20837757)
Yes, you have to use a forked SQLite in order to make use of dqlite.

I believe they (the LXD team) are working on upstreaming the WAL changes but due to SQLite's very strong compatibility guarantees they want to be very certain the API and protocol are correct before carving it in stone. Not to mention they are the only major users of the feature, so more widespread use would also be nice before merging it upstream.

Re:Dqlite – High-Availability SQLite by free-ekanayaka on Friday August 30, 2019 @11:14AM (#20839400)
Everything you said is very accurate (dqlite author here).
Re:Dqlite – High-Availability SQLite by tyingq on Friday August 30, 2019 @07:48AM (#20837643)
They would have to, wouldn't they? The Sqlite VFS subsystem is the obvious place to intercept the usually local DB and WAL reads/writes and make them distributed functions that use Raft.