Comments - TokuDB Differences
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
I'm pretty sure this is a complete list of clarifications and additional changes between the TokuDB from Tokutek and the version from MariaDB.org.
- No "INSERT NOAR" or "UPDATE NOAR" means that Fast Upserts and Fast Updates are not possible. - No Hot Indexing (creating indexes while the table is available for insert/update/delete) - Index creation will force a complete table rewrite (table is read-only for the duration of the operation as it is rebuilt, all existing indexes are recreated, and new index is created) - Auto-increment behavior is as implemented in MyISAM, not TokuDB - DDL grammar changes. I'm not sure of the specifics but I believe the clustering keyword for index creation and how you specify compression type is different. - Memory Allocator. We ship MySQL and MariaDB with jemalloc statically linked to mysqld.