3 ms·
That's the whole thing with the difference between so-called "ACID" databases and MySQL. Corrupted data after a power outage just shouldn't happen. It's one of
by doctor_eval 5y ago
That's the whole thing with the difference between so-called "ACID" databases and MySQL. Corrupted data after a power outage just shouldn't happen. It's one of the things database engines are supposed to protect us against.
In 30 years, it's never happened to me with Postgres or the other two database engines I've used professionally.
If it did happen, then most people who know about databases would say "that's a pretty poor database".
- willvarfar 5y agoMySQL is, by default, ACID. There are storage engines that aren't, but they are rare and not default choices.
- EdwardDiego 5y agoMyISAM used to be the default for a long while. I made a bit of extra money when younger tidying up MySQL DBs that were in inconsistent states thanks to MyISAM not enforcing FKs.
- hu3 5y agoInnoDB has been the default for over a decade.
- doctor_eval 5y agoBut the dominance of MySQL and LAMP happened long before InnoDB.
- EdwardDiego 5y agoYep, it is now. My favourite bit was when InnoDB became the default, a lot of people configured MySQL after upgrading to keep defaulting MyISAM "for performance" that they really didn't need.
- fasteo 5y ago>>> That's the whole thing with the difference between so-called "ACID" databases and MySQL. Corrupted data after a power outage just shouldn't happen. It's one of the things database engines are supposed to protect us against. I knew I was not running MySQL in ACID mode (via innodb-flush-log-at-trx-commit=0), and I sacrificed safety by performance. I was OK with that in my specific use-case.