Molina documentation
Test data durability under a power cut
A database telling you a write is saved is a promise. A power cut finds out whether it was true. Ordinary tests run on a computer whose disk keeps its word, so they never ask the question.
Molina cuts the power at a chosen request while your software runs in a world. The disk can be made to say saved before the write is on the platter, which a real disk with a cache can do.
What the runs showed
Postgres 17, with fsync, synchronous commit and full page writes on, ran against a disk that lied about flushes. After the power cut the application had been told 85 commits were saved and 63 were gone. The database came back with its table. What survived was a prefix of the rows.
QuestDB was cut at 40 points of its workload. Five cuts were silent losses: the table was not suspended and the commits made after the restart were gone. In the case the gate kept, six new commits were acknowledged and the read back failed.
The limits
One version of each database, one machine, one image pulled by digest. The Postgres figures come from a separate gate run, not the exact replay run, and the count of commits told moves between its runs. These are my runs, not a rate.