Mysql engines: Difference between revisions
From wikinotes
(Created page with "Each table can have it's own engine,<br> performance may suffer if a join is made across two engine types. {| class="wikitable" |- | innodb || write/concurrency optimized (row lock on write) |- | myisam || read optimized (table lock on write) |- | memory || slow, only supports hash indexes, used for temporary tables. |- | federated || defers reads/writes to other databases. slow on joins, aggregates, etc. |- | blackhole || writes not persisted. |- | csv || csvs written...") |
No edit summary |
||
| Line 2: | Line 2: | ||
performance may suffer if a join is made across two engine types. | performance may suffer if a join is made across two engine types. | ||
= Documentation = | |||
<blockquote> | |||
{| class="wikitable" | |||
|- | |||
| InnoDB || https://dev.mysql.com/doc/refman/5.7/en/innodb-storage-engine.html | |||
|- | |||
|} | |||
</blockquote><!-- Documentation --> | |||
= Notes = | |||
<blockquote> | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| Line 17: | Line 28: | ||
|- | |- | ||
|} | |} | ||
</blockquote><!-- Notes --> | |||
Latest revision as of 02:59, 8 September 2022
Each table can have it's own engine,
performance may suffer if a join is made across two engine types.
Documentation
InnoDB https://dev.mysql.com/doc/refman/5.7/en/innodb-storage-engine.html
Notes
innodb write/concurrency optimized (row lock on write) myisam read optimized (table lock on write) memory slow, only supports hash indexes, used for temporary tables. federated defers reads/writes to other databases. slow on joins, aggregates, etc. blackhole writes not persisted. csv csvs written to a special directory automatically become tables
