1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
Innobase
========
The Innobase plugin provides the InnoDB storage engine. It is almost identical
to the innodb_plugin, but adapted to Drizzle. We plan to move to having InnoDB
provided by the HailDB plugin, which will allow for easier maintenance and
upgrades.
InnoDB is the default storage engine for Drizzle. It is a fully transactional
MVCC storage engine.
innodb_plugin origins
---------------------
We maintain the Innobase plugin in Drizzle as a downstream project of the
innodb_plugin for MySQL. We try and keep it up to date with innodb_plugin
releases.
Differences from innodb_plugin
------------------------------
* AUTO_INCREMENT behaves the standard way (as in MyISAM)
* Supports four byte UTF-8 with the same index size
AIO support
-----------
InnoDB supports Linux native AIO when compiled on platforms that have the
libaio development files installed (typically a package called libaio-dev or
libaio-devel). For more information on the advantages of this please see
http://blogs.innodb.com/wp/2010/04/innodb-performance-aio-linux/
To confirm that Linux native AIO is enabled execute this command:
.. code-block:: mysql
show global variables like 'innodb_use_native_aio';
Compatibility with MySQL
------------------------
Although the innobase plugin is near identical to the innodb_plugin in MySQL,
the on disk formats are slightly incompatible (to allow for the same index
length for the four byte UTF-8 that Drizzle supports) and the table definitions
(FRM for MySQL, .dfe for Drizzle) are completely different. This means that you
cannot directly share InnoDB tablespaces between MySQL and Drizzle. Use the
drizzledump tool to migrate data from MySQL to Drizzle.
InnoDB Transaction Log
----------------------
The Innobase plugin provides a mechanism to store replication events in an
InnoDB table. When enabled, this transaction log can be accessed through
the SYS_REPLICATION_LOG and INNODB_REPLICATION_LOG tables in the DATA_DICTIONARY
schema.
To enable this transaction log, you must start the server with:
**--innodb.replication-log=true**
It is not enabled by default.
|