It would be great if SQLlite could provide the option of "NOSYNC" tables that might lose recent updates after a crash. However, in order to ensure that the on-disk file is consistent it at least needs write ordering when it does decide to write to disk - "I don't care when this write gets to disk, as long as when it does, this other write has already gotten there too". There's no API to request that without also requesting data be flushed to permanent storage immediately - be it fsync, sync_file_range or O_DIRECT.