MariaDB: Difference between revisions
m Changed InnoDB section to reflect MariaDB |
m A few more MySQL's missed, website changed |
||
| Line 72: | Line 72: | ||
=== Binary logging === | === Binary logging === | ||
MariaDB by default turns on a feature called binary logging. This makes it so that every transaction within the database, including the data, is stored in a binary log. That way, if you are running more than 1 | MariaDB by default turns on a feature called binary logging. This makes it so that every transaction within the database, including the data, is stored in a binary log. That way, if you are running more than 1 MariaDB server in a master-slave configuration, you can link them together and the slave reads the logs to get the same data. You more than likely won't need this if you are running a standalone MariaDB setup. The problems with this implementation are: | ||
* MariaDB has to write the transaction twice, once to the table and once to the log. This slows things down. | * MariaDB has to write the transaction twice, once to the table and once to the log. This slows things down. | ||
* MariaDB has data stored in 2 places, doubling the disk space for each write. This is also a security issue if working with sensitive data. | * MariaDB has data stored in 2 places, doubling the disk space for each write. This is also a security issue if working with sensitive data. | ||
| Line 122: | Line 122: | ||
== External Links == | == External Links == | ||
* [ | * [https://mariadb.org/ MariaDB website] | ||