Tagged with "acid"
Fun MySQL fact of the day: binlog cache
By now, I think we have a shared understanding that the binary log is an important feature in MySQL. And maybe, you may have been wondering, "how does the binary log get recorded"? And that's a good question with a couple fun facts we'll look at next! ... read moreFun MySQL fact of the day: implicit rollbacks
Last Thursday, I suggested that you may not always want your transactions automatically rolled-back on an ACID violation, and, on Monday, I hinted that transaction rollbacks are nearly the most expensive thing you can do in MySQL/InnoDB. And, well, it's because of the very same "undo logs" about ... read moreFun MySQL fact of the day: all-or-something?
Finally,A. The A in ACID stands for Atomicity, which is the property that guarantees that a series of database operations performed in a transaction all occur or nothing occurs. You might be thinking, "if Atomicity is the first letter in ACID, why did you save it ... read more
Fun MySQL fact of the day: inconsistent consistency
In being consistency inconsistent, theC in ACID and the C in CAP both stand for Consistency, but don't describe the same properties. In fact, the C in CAP actually stands for Atomic Consistency (or Linearizability), and, oh holy crap!, the Atomic part of Atomic Consistency isn't the ... read more
Fun MySQL fact of the day: InnoDB read-only optimisation
TheI in ACID stands for Isolation, which is a property that determines whether or not a transaction can see the progress of other transactions. Transaction isolation is a complex system generally defined by the allowance of certain "read phenomena". ... read more
Fun MySQL fact of the day: sync_binlog is a counter
The D in ACID stands for Durability, which is the property that guarantees a committed transaction will be permanently recorded. Perfect durability is impossible, but MySQL allows us to improve our ability to offer this guarantee this through the sync_binlog flag. ... read more