20 ms·
This is likely to happen in the case that your hardware is telling lies about when it has committed data to disk. In this case, it makes sense to cut short the
by Andys 2y ago
This is likely to happen in the case that your hardware is telling lies about when it has committed data to disk.
In this case, it makes sense to cut short the WAL application, but you are probably right in saying it should throw an error (or at least a warning).
- ncruces 2y agoYou're right that write reordering might cause this (an invalid frame followed by a few valid frames). That shouldn't happen if you use PRAGMA synchronous=FULL, but in WAL mode it's very common to use NORMAL. Not sure what's the better strategy here, but I'd definitely appreciate a mode that warns me before silently truncating a WAL that has valid frames in it.