Have now implemented a version of this at https://github.com/michalc/sqlite-memory-vfs/blob/74a24ce567557d72eebf73fbdf6d8e609aedafe3/sqlite_memory_vfs.py#L112-L

Have now implemented a version of this at https://github.com/michalc/sqlite-memory-vfs/blob/74a24ce567557d72eebf73fbdf6d8e609aedafe3/sqlite_memory_vfs.py#L112-L155 https://github.com/michalc/sqlite-memory-vfs/blob/74a24ce567... I think different to yours in two ways: - If doesn't go via PENDING if it doesn't need to. Not sure what's best really - but since RESERVED can already be skipped in some cases (recovering from a hot-journal) then so far happy with "skipping is a thing", and PENDING is private to the VFS anyway from what I can tell, so nothing else should care I think - It doesn't do the blocking in the lock function, but depends on SQLite's core code doing it via the busy handler/timeout