3 ms·
Write-ahead-logging has existed for how many years now? It disappoints me (but doesn't surprise me, unfortunately) that unexpected record truncation is still an
by quanticle 13y ago
Write-ahead-logging has existed for how many years now? It disappoints me (but doesn't surprise me, unfortunately) that unexpected record truncation is still an issue that we have to deal with.
- Confusion 13y agoHow does write-ahead-logging deal with unexpected record truncation in the log?
- twic 13y agoIf an entry in the log is corrupt, it doesn't get replayed. The filesystem is left in a consistent state, just without that data.
- Confusion 13y agoIf an entry in the log is corrupt, it doesn't get replayed. Yes, and that is exactly the solution the article calls for: you have to design your log format so you can determine a log entry is corrupt, so you don't replay it, while still replaying the remaining entries. You can't solve that using write-ahead-logging, or it'd be turtles all the way down.