3 ms·
Database engines that live as libraries inside application processes (like WT) have a more pressing need for checksums because the most common attack vector is
by dboreham 2y ago
Database engines that live as libraries inside application processes (like WT) have a more pressing need for checksums because the most common attack vector is buggy pointer arithmetic outside the library that stomps on data in memory randomly.
- whizzter 2y agoChecksumming is also useful when storage goes bad or other random hardware corruption like cosmic rays or overheating/old computers.
- pixl97 2y agoThis reminds me of the time I had a disk go 'random' in a RAID. Disk didn't fail, instead it just returned junk for every Nth read. Happened to be in a big database server too. Crazy part is it took far longer than I would have expected to catch data showing up corrupted in user applications so an entire 28 hours of data had to be rolled back.