Author: MariaDB Knowledge Database

Feed: MariaDB Knowledge Base Article Feed. Author: . Contents Generic Backup Process with Storage Snapshots The BACKUP STAGE commands are a set of commands to make it possible to make an efficient external backup tool. These commands could even be used by tools that perform backups by taking a snapshot of a file system, SAN, or some other kind of storage device. Generic Backup Process with Storage Snapshots A tool that backs up MariaDB by taking a snapshot of a file system, SAN, or some other kind of storage device could use each BACKUP STAGE command in the following way: ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . The BACKUP STAGE commands are a set of commands to make it possible to make an efficient external backup tool. How Mariabackup uses these commands depends on whether you are using the version that is bundled with MariaDB Community Server or the version that is bundled with MariaDB Enterprise Server. Mariabackup and BACKUP STAGE Commands in MariaDB Community Server The version of Mariabackup that is bundled with MariaDB Community Server does not yet use the BACKUP STAGE commands in an efficient way. In that version, instead of executing the FLUSH TABLES WITH ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . This is how the REST feature can be added as a library called by an OEM table. Before making the REST OEM module, the Microsoft Casablanca package must be installed as for compiling MariaDB from source. Even if this module is to be used with a binary distribution, you need some CONNECT source files in order to successfully make it. It is made with four files existing in the version 1.06.0010 of CONNECT: tabrest.cpp, restget.cpp, tabrest.h and mini-global.h. It also needs the CONNECT header files that are included in tabrest.cpp and the ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . Starting with CONNECT version 1.06.0010, JSON, XML and possibly CSV data files can be retrieved as results from REST queries when creating or querying such tables. However, because this feature uses the Microsoft Casablanca (cpprestsdk) package, it is not included in the binary distributions of MariaDB. To get this feature, it is necessary to compile MariaDB from source. First, install the package as explained in https://github.com/microsoft/cpprestsdk. Then get the source and make, compile and install MariaDB as explained in the MariaDB documentation. The result should be a MariaDB version with CONNECT having ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . When a transaction updates a row in an InnoDB table, InnoDB's MVCC implementation keeps old versions of the row in the InnoDB undo log. The old versions are kept at least until all transactions older than the transaction that updated the row are no longer open. At that point, the old versions can be deleted. InnoDB has purge process that is used to delete these old versions. Optimizing Purge Performance Configuring the Purge Threads The number of purge threads can be set by configuring the innodb_purge_threads system variable. This system variable can ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . This page documents system variables related to Galera Cluster. For options that are not system variables, see Galera Options. See Server System Variables for a complete list of system variables and instructions on setting them. Also see the Full list of MariaDB options, system and status variables. wsrep_auto_increment_control Description: If set to 1 (the default), will automatically adjust the auto_increment_increment and auto_increment_offset variables according to the size of the cluster, and when the cluster size changes. This avoids replication conflicts due to auto_increment. In a master-slave environment, can be set to OFF ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . MariaDB's data-at-rest encryption requires the use of a key management and encryption plugin. These plugins are responsible both for the management of encryption keys and for the actual encryption and decryption of data. MariaDB supports the use of multiple encryption keys. Each encryption key uses a 32-bit integer as a key identifier. If the specific plugin supports key rotation, then encryption keys can also be rotated, which creates a new version of the encryption key. The Eperi Key Management plugin is a key management and encryption plugin that integrates with eperi Gateway ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . The COMPRESSED row format is similar to the COMPACT row format, but tables using the COMPRESSED row format can store even more data on overflow pages than tables using the COMPACT row format. This results in more efficient data storage than tables using the COMPACT row format, especially for tables containing columns using the VARBINARY, VARCHAR, BLOB and TEXT data types. The COMPRESSED row format also supports compression of all data and index pages. The COMPRESSED row format was originally introduced in MySQL 5.5 and MariaDB 5.5. Using the COMPRESSED Row Format ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . The DYNAMIC row format is similar to the COMPACT row format, but tables using the DYNAMIC row format can store even more data on overflow pages than tables using the COMPACT row format. This results in more efficient data storage than tables using the COMPACT row format, especially for tables containing columns using the VARBINARY, VARCHAR, BLOB and TEXT data types. However, InnoDB tables using the COMPRESSED row format are more efficient. The DYNAMIC row format was originally introduced in MySQL 5.5 and MariaDB 5.5. Using the DYNAMIC Row Format MariaDB starting ... Read More

Feed: MariaDB Knowledge Base Article Feed. Author: . The COMPACT row format is similar to the REDUNDANT row format, but it stores data in a more compact manner that requires about 20% less storage. This row format was originally introduced in MySQL 5.0.3. Using the COMPACT Row Format MariaDB starting with 10.2.2In MariaDB 10.2.2 and later, the easiest way to create an InnoDB table that uses the COMPACT row format is by setting the ROW_FORMAT table option to to COMPACT in a CREATE TABLE or ALTER TABLE statement. It is recommended to set the innodb_strict_mode system variable to ON when ... Read More