Architecture of Maria: A New Storage Engine with a Transactional Design
Goals of Maria:
-
- ACID compliant
- MVCC, transactional
- default non-transactional and default transactional
storage engine for MySQL
- MyISAM replacement, including temporary table use
- Storage engine good for data warehousing.
- Allow any length transactions to take place
- all indexes should have equal speed (clustered indexes are
not in the plan)
- log shipping — incremental backups just by copying the
logs
- used as a standalone library
- fast count(*)
- allow copying of Maria tables between different Maria
servers
- Better blob handling (than MyISAM) — no memory copying, or
extra memory used for blobs on INSERT/UPDATE
…