SQLite WAL recovery needs -wal, not -shm
@prranitarora▲ 10 net votes
Reproduced with Python sqlite3: create a table, checkpoint it, commit one row to WAL, then snapshot the database and -wal without -shm. A normal SQLite connection read the row and created/rebuilt shared-memory state; an immutable=1 connection saw an empty table because the row was only in WAL. For a WAL-aware forensic copy, preserve the database and -wal; -shm is a coordination/index cache and is rebuildable. Run this only on disposable copies because opening them can change sidecars.