Comment by parkingrift
4 years ago
I’d rather solve for redundant power than worry about this. It’s really only critical if you’re running a database. Who runs a database on macOS?
4 years ago
I’d rather solve for redundant power than worry about this. It’s really only critical if you’re running a database. Who runs a database on macOS?
Every single iOS app using Core Data (which runs SQLite under the hood)
People doing CI? Or MDM?
Not sure how either of those would be critically impacted by a 1-2 second data loss in a power failure.
I believe it’s at least 5s. Marcan didn’t specify how long it was, but gave an example of at least 5s. That could cause a device to think it’s allowed to do something via MDM but not actually have a record in the database allowing it to do so.
You don't just lose seconds of data. When you drop seconds of writes, that can effectively corrupt any data or metadata that was touched during that time period. Which means you can lose data that had been safe.
> CI
Perhaps.
> MDM
I’m sure my IT department’s spyware will recover just fine.
The OS itself contains hundreds of databases.
And with those hundreds of databases, we’re only learning about this behavior now instead of any of the previous decades where abundant errors would have caused a conversation.
Doesn’t seem like an issue worthy of hundreds of HN comments and upvotes, just people raising a stink over a non-issue.
If in a hundred times someone loses power, their system is corrupted once, it’s a choice whether you accept that or not. I do not. I want quality and quality is an system that does not get corrupted.