3 ms·
I'm just speculating here, but in a normal database you would have different processes writing the wal files to the database or archives. You don't have that w
by forinti 3y ago
I'm just speculating here, but in a normal database you would have different processes writing the wal files to the database or archives.
You don't have that with sqlite, so I don't see an obvious advantage for this, except if they now spawn a process or thread to do this concurrently.
Edit: so I read the doc (shame on me) and it has nothing to do with speed. Its purpose is to prevent a wal file from growing too large.
- hahn-kev 3y agoI believe SQLite supports accessing a single database file from multiple processes or threads at once
- arcbyte 3y agoThere can be many readers simultaneously, but only ever one writer at a time.
- WolfOliver 3y agoI guess it is to make it crash save, e.g. in case the server dies in the middle of a write, the database would be corrupt after restart, with the wal file it can recover.
- deleted 3y ago[deleted]