MariaDB MariaDB 10.3.7 GA Release !

eva2000 · May 28, 2018

MariaDB 10.3.7 GA release has been announced with release of MariaDB 10.3.7. What's New in MariaDB Server 10.3 | MariaDB ! Get a full list of features in MariaDB Server 10.3.

We are happy to announce the general availability (GA) of MariaDB Server 10.3! This release is a big milestone for the development of MariaDB Server and is the result of a huge effort by the development team and contributors – thanks to everyone involved! With our previous major release of MariaDB Server 10.2 last year, we started a journey of adding more enterprise-grade features to better close the gap with proprietary databases.
Click to expand...

The key enhancements of MariaDB Server 10.3 can be put in the following categories:

Temporal data processing (system-versioned tables)

Oracle compatibility features

Purpose-built storage engines

Click to expand...

Purpose built storage engines are interesting with MyRocks and Spider

Purpose-Built Storage Engines
At MariaDB, we believe in using the right tool for the right trade. However, we don’t feel that you need to change everything in order to achieve that. We have a unique architecture with pluggable storage engines that allows the user to adapt the database to the use case and workload without changing the main characteristics and features. We believe that this flexibility serves the best interest of the user and we will work on further advancing this with future versions of MariaDB. This architecture will enable both the community and our team to innovate further by adding storage engines designed for new hardware and new use cases. In MariaDB Server 10.3, we introduce two new storage engines that are declared stable, MyRocks and Spider.

MyRocks comes from a collaboration with Facebook where the storage engine is built on top of RocksDB – an open source project mainly maintained by Facebook. The MyRocks storage engine is built using a log-structured merge tree (LSM tree) architecture and is well adapted to high write workloads. MyRocks also has a very high compression ratio and is built to optimize the lifetime of SSD disks.

Spider is a storage engine designed for extreme scale. The Spider storage engine allows you to shard a specific table across multiple nodes. It uses the partitioning protocol to define how the table should be split up and each individual shard will then reside on a remote MariaDB Server that will only handle queries for that particular shard. With Spider you get almost linear scaling for INSERTS and key lookup read queries.
Click to expand...

Changes & Improvements in MariaDB 10.3

MariaDB 10.3 is the current major stable version. It will be supported until May 2023.
Click to expand...

Implemented Features
Syntax / General Features

System-versioned tables (also known as AS OF) (MDEV-12894)

Table Value Constructors (MDEV-12172) — GSoC 2017 project by Galina Shalygina

Transform [NOT] IN predicate with long list of values INTO [NOT] IN subquery (MDEV-12176) — GSoC 2017 project by Galina Shalygina

ROW TYPE OF now supports local SP variables (MDEV-14139)

Aggregate stored functions (MDEV-7773) — GSoC 2016 project by Varun Gupta

Support for LIMIT clause in GROUP_CONCAT() (MDEV-11297)

PERCENTILE_CONT, PERCENTILE_DISC, and MEDIAN window functions (MDEV-12985)

FOR ... END FOR statement (MDEV-14415)

XA RECOVER FORMAT='SQL' (MDEV-14593)

Oracle compatible SUBSTR() function (MDEV-14012) — contribution by Jérôme Brauge

INVISIBLE columns (MDEV-10177) — GSoC 2016 project by Sachin Setiya

Various scalability improvements (MDEV-14529, MDEV-14505)

Sequences can now be used with DEFAULT.

Semi-sync plugin merged into the server (MDEV-13073) — contribution by Alibaba

CREATE SEQUENCE (MDEV-10139)

SHOW CREATE SEQUENCE

ALTER SEQUENCE

DROP SEQUENCE

NEXT VALUE FOR

PREVIOUS VALUE FOR

SETVAL()

INTERSECT and EXCEPT. These are both now reserved words and can no longer be used as an identifier without being quoted (MDEV-10141)

ROW data type for stored routine variables (MDEV-10914, MDEV-12007, MDEV-12291)

TYPE OF and ROW TYPE OF anchored data types for stored routine variables (MDEV-12461)

Cursors with parameters (MDEV-12457)

DDL Fast Fail - WAIT/NOWAIT (MDEV-11379, MDEV-11388)

CHR() function (MDEV-12685)

DELETE statement can delete from the table that is used in a subquery in the WHERE clause (MDEV-12137)

Stored routine parameters can use ROW TYPE OF (MDEV-13581)

The server now supports the PROXY protocol - see also the new proxy_protocol_networks system variable (MDEV-11159)

Instant ADD COLUMN (MDEV-11369) — Tencent Game DBA Team, developed by vinchen.

UPDATE statements with the same source and target (MDEV-12874) — from Jerome Brauge.

ORDER BY and LIMIT in multi-table update (MDEV-13911)

DATE_FORMAT(date, format, locale) - 3 argument form of DATE_FORMAT (MDEV-11553)

The MariaDB SQL/PL stored procedure dialect (enabled with sql_mode=ORACLE) now supports Oracle style packages. Support for the following statements has been added (MDEV-10591):

CREATE PACKAGE

CREATE PACKAGE BODY

DROP PACKAGE

DROP PACKAGE BODY

SHOW CREATE PACKAGE

SHOW CREATE PACKAGE BODY

New sql_mode SIMULTANEOUS_ASSIGNMENT to make the SET part of the UPDATE statement evaluate all assignments simultaneously, not left-to-right.

Correctness improvement - TRUNCATE honors transactional locks (MDEV-15061)

Windows binaries now use high-precision timer when available (MDEV-15694). This makes much less probable for two queries to have the same CURRENT_TIMESTAMP(6) value, for example.

Two new ALTER TABLE ... ALGORITHM options, INSTANT and NOCOPY, which allow operations that would require any data files to be modified, or that would require rebuilding the clustered index respectively, to be refused rather than potentially perform slowly (MDEV-13134)

Compatibility

As a result of implementing Table Value Constructors, the VALUES function has been renamed to VALUE() (MDEV-12172)

When running with sql_mode=ORACLE, the server now understands a subset of Oracle's PL/SQL language instead of the traditional MariaDB syntax for stored routines. See MDEV-10142, MDEV-10764 and SQL_MODE=ORACLE From MariaDB 10.3 to know the current status.

New sql_mode, EMPTY_STRING_IS_NULL.

INTERSECT and EXCEPT are both now reserved words and can no longer be used as an identifier without being quoted (MDEV-10141)

Compression

Storage-engine Independent Column Compression (MDEV-11371) — Tencent Game DBA Team, developed by willhan, also thanks to AliSQL.

On Linux, shrink the core dumps by omitting the InnoDB buffer pool (MDEV-10814)

Encryption

Temporary files created by merge sort and row log are encrypted if innodb_encrypt_log is set to 1, regardless of whether the table encrypted or not (MDEV-12634).

Optimizer/Performance

Condition pushdown through PARTITION BY clause of window functions (MDEV-10855)

New optimizer switch setting, split_grouping_derived=on (see description)

Numerous performance improvements for high-concurrency load

Numerous scalability and performance improvements to global data structures, including MDEV-14756, MDEV-15019, MDEV-14482, MDEV-15059, MDEV-15104

Performance improvements to persistent data structures: MDEV-15090, MDEV-15132

Storage Engines
InnoDB

innodb_fast_shutdown now has a new mode, 3, which skips the rollback of connected transactions (MDEV-15832)

Spider
The Spider storage engine has been updated to 3.3.13. The partitioning storage engine has been updated to support all the new Spider features including:

Direct join support. This allows Spider to do JOINS and GROUP BYs internally.

Direct update and delete.

Direct aggregates.

slave_transaction_retry_errors and slave-transaction-retry-interval allow more control over handling delays or conflicts when applying binary logs.

Most of the features were done as part of MDEV-7698.

OQGRAPH

OQGraph now supports the "leaves" algorithm (MDEV-11271) — contribution by Heinz Wiesinger

Partition Engine

Numerous improvements for the partition engine (MDEV-7698) — contribution by Kentoku Shiba

Full text support.

Multi-range-read (Gives better performance when handling multiple ranges).

Support for condition pushdown.

HANDLER support

Aggregate pushdown

Bulk update/delete

Information Schema

The Information Schema is optimized to use much less memory when selecting from INFORMATION_SCHEMA.TABLES or any other table with many VARCHAR or TEXT columns (MDEV-14275)

The Information Schema Columns table now displays system versioning info in the EXTRA column - MDEV-15062

Logging

Disable logging of certain statements to the general log or the slow query log with the log_disabled_statements and log_slow_disabled_statements system variables.

A new option to log_slow_filter, filsort_priority_queue.

Replication

Per-engine mysql.gtid_slave_pos tables (MDEV-12179) — Implemented by Kristian Nielsen funded by Booking.com.

Data Type API
10.3 continues refactoring for the data type API started in 10.2, which will make it possible to have user data type plugins. This work is still in progress (see MDEV-4912 for the current status and subtasks). Most of the task in this category do not change the server behavior. Some tasks do have a visible effect.

Idle Transactions
Connections with idle transactions can be automatically killed after a specified time period by means of the idle_transaction_timeout, idle_readonly_transaction_timeout and idle_write_transaction_timeout system variables.

System Variables
For a list of all new variables, see System Variables Added in MariaDB 10.3 and Status Variables Added in MariaDB 10.3.

New system variable gtid_pos_auto_engines.

session variables tracking is enabled by default (MDEV-11825)

Remove deprecated variables innodb_file_format, innodb_file_format_check, innodb_file_format_max and innodb_large_prefix.

version_source_revision - permits seeing which version of the source was used for the build (MDEV-12583).

Added bind_address as a system variable (MDEV-12542).

The max value of the max_prepared_stmt_count system variable has been increased from 1048576 to 4294967295

The proxy_protocol_networks variable can now be modified without restarting the server (MDEV-15501)

Comparison with MySQL

System Variable Differences Between MariaDB 10.3 and MySQL 5.7

Click to expand...

eva2000 · May 28, 2018

Centmin Mod 123.09beta01 preview

Code (Text):

--------------------------------------------------------
     Centmin Mod Menu 123.09beta01 centminmod.com
--------------------------------------------------------
1).  Centmin Install
2).  Add Nginx vhost domain
3).  NSD setup domain name DNS
4).  Nginx Upgrade / Downgrade
5).  PHP Upgrade / Downgrade
6).  XCache Re-install
7).  APC Cache Re-install
8).  XCache Install
9).  APC Cache Install
10). Memcached Server Re-install
11). MariaDB MySQL Upgrade & Management
12). Zend OpCache Install/Re-install
13). Install/Reinstall Redis PHP Extension
14). SELinux disable
15). Install/Reinstall ImagicK PHP Extension
16). Change SSHD Port Number
17). Multi-thread compression: pigz,pbzip2,lbzip2...
18). Suhosin PHP Extension install
19). Install FFMPEG and FFMPEG PHP Extension
20). NSD Install/Re-Install
21). Update - Nginx + PHP-FPM + Siege
22). Add Wordpress Nginx vhost + Cache Plugin
23). Update Centmin Mod Code Base
24). Exit
--------------------------------------------------------
Enter option [ 1 - 24 ] 11
--------------------------------------------------------

New submenu option 7

Code (Text):

--------------------------------------------------------
     MariaDB MySQL Upgrade & Management Sub-Menu 
--------------------------------------------------------
0). Regenerate New MySQL Root User Password (local server)
1). MariaDB 5.2.x Branch Upgrade Only
2). MariaDB 5.2.x to MariaDB 5.5 YUM upgrade
3). MariaDB 5.5 to MariaDB 10.x YUM upgrade
4). MariaDB 5.5 to MariaDB 10.1.x YUM upgrade
5). MariaDB 10.x to MariaDB 10.1.x YUM upgrade
6). MariaDB 10.1.x to MariaDB 10.2.x YUM upgrade
7). MariaDB 10.2.x to MariaDB 10.3.x YUM upgrade
8). Back to Main menu
--------------------------------------------------------
Enter option [ 0 - 8 ]

Yes you'd need to update progressively from MariaDB 10.1 > 10.2 > 10.3 which is best practice always.

Code (Text):

--------------------------------------------------------
     MariaDB MySQL Upgrade & Management Sub-Menu 
--------------------------------------------------------
0). Regenerate New MySQL Root User Password (local server)
1). MariaDB 5.2.x Branch Upgrade Only
2). MariaDB 5.2.x to MariaDB 5.5 YUM upgrade
3). MariaDB 5.5 to MariaDB 10.x YUM upgrade
4). MariaDB 5.5 to MariaDB 10.1.x YUM upgrade
5). MariaDB 10.x to MariaDB 10.1.x YUM upgrade
6). MariaDB 10.1.x to MariaDB 10.2.x YUM upgrade
7). MariaDB 10.2.x to MariaDB 10.3.x YUM upgrade
8). Back to Main menu
--------------------------------------------------------
Enter option [ 0 - 8 ] 7
--------------------------------------------------------
Need to be on MariaDB 10.2 before updating to MariaDB 10.3

MariaDB 10.1 to 10.2 update via submenu option 6 (disabling the beta testing message which is in place right now)

Code (Text):

--------------------------------------------------------
     MariaDB MySQL Upgrade & Management Sub-Menu  
--------------------------------------------------------
0). Regenerate New MySQL Root User Password (local server)
1). MariaDB 5.2.x Branch Upgrade Only
2). MariaDB 5.2.x to MariaDB 5.5 YUM upgrade
3). MariaDB 5.5 to MariaDB 10.x YUM upgrade
4). MariaDB 5.5 to MariaDB 10.1.x YUM upgrade
5). MariaDB 10.x to MariaDB 10.1.x YUM upgrade
6). MariaDB 10.1.x to MariaDB 10.2.x YUM upgrade
7). MariaDB 10.2.x to MariaDB 10.3.x YUM upgrade
8). Back to Main menu
--------------------------------------------------------
Enter option [ 0 - 8 ] 6
--------------------------------------------------------

-------------------------------------------------------------------------------
 This script's MariaDB 10.2.x upgrade process is still in beta testing stages.
 So please test on a test server and not a live production server. But if you use
 on live server or if MySQL databases already exist, please back them up before
 running this upgrade script via mysqldump - instructions at:
 http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html.

 ###################################################################
 ###          IMPORTANT MYSQLDUMP BACKUP BEFORE UPGRADE          ###
 ###        OR RISK DATA LOSS DUE TO MARIADB 10.2 Changes        ###
 ###################################################################

 For each DATABASENAME backup via mysqldump i.e.

  mysqldump --opt --routines DATABASENAME > /path/to/DATABASENAME_backup.sql
------------------------------------------------------------------------

Code (Text):

Have you backed up your databases ? [y/n] y

MariaDB 10.2.x https://mariadb.com/kb/en/mariadb/what-is-mariadb-102/

!!  Note  !!
upgrade process can take more >5 minutes.. you may want to shutdown
nginx server to not show mysql errors to visitors on your site or
put site(s) into maintenance mode before proceeding with mysql upgrade

Do you want to continue with upgrade to MariaDB 10.2.x ? [y/n] y

Ta da ! MariaDB 10.2 updated

Code (Text):

mysqladmin ver
mysqladmin  Ver 9.1 Distrib 10.2.15-MariaDB, for Linux on x86_64
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Server version          10.2.15-MariaDB
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /var/lib/mysql/mysql.sock
Uptime:                 7 sec

Threads: 5  Questions: 2  Slow queries: 0  Opens: 17  Flush tables: 1  Open tables: 11  Queries per second avg: 0.285

Now try submenu option 7 for MariaDB 10.2 to 10.3 and will be greeted with beta testing message while I figure out and test and optimise MariaDB 10.3 config settings privately

Code (Text):

--------------------------------------------------------
     MariaDB MySQL Upgrade & Management Sub-Menu  
--------------------------------------------------------
0). Regenerate New MySQL Root User Password (local server)
1). MariaDB 5.2.x Branch Upgrade Only
2). MariaDB 5.2.x to MariaDB 5.5 YUM upgrade
3). MariaDB 5.5 to MariaDB 10.x YUM upgrade
4). MariaDB 5.5 to MariaDB 10.1.x YUM upgrade
5). MariaDB 10.x to MariaDB 10.1.x YUM upgrade
6). MariaDB 10.1.x to MariaDB 10.2.x YUM upgrade
7). MariaDB 10.2.x to MariaDB 10.3.x YUM upgrade
8). Back to Main menu
--------------------------------------------------------
Enter option [ 0 - 8 ] 7
--------------------------------------------------------
Place holder for now until MariaDB 10.3.x is ready to be added

Disabling the beta testing message for submenu option 7 for MariaDB 10.2 to 10.3 test update

Code (Text):

--------------------------------------------------------
     MariaDB MySQL Upgrade & Management Sub-Menu    
--------------------------------------------------------
0). Regenerate New MySQL Root User Password (local server)
1). MariaDB 5.2.x Branch Upgrade Only
2). MariaDB 5.2.x to MariaDB 5.5 YUM upgrade
3). MariaDB 5.5 to MariaDB 10.x YUM upgrade
4). MariaDB 5.5 to MariaDB 10.1.x YUM upgrade
5). MariaDB 10.x to MariaDB 10.1.x YUM upgrade
6). MariaDB 10.1.x to MariaDB 10.2.x YUM upgrade
7). MariaDB 10.2.x to MariaDB 10.3.x YUM upgrade
8). Back to Main menu
--------------------------------------------------------
Enter option [ 0 - 8 ] 7
--------------------------------------------------------

Code (Text):

-------------------------------------------------------------------------------
 This script's MariaDB 10.3.x upgrade process is still in beta testing stages.
 So please test on a test server and not a live production server. But if you use
 on live server or if MySQL databases already exist, please back them up before
 running this upgrade script via mysqldump - instructions at:
 http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html.

 ###################################################################
 ###          IMPORTANT MYSQLDUMP BACKUP BEFORE UPGRADE          ###
 ###        OR RISK DATA LOSS DUE TO MARIADB 10.3 Changes        ###
 ###################################################################

 For each DATABASENAME backup via mysqldump i.e.

  mysqldump --opt --routines DATABASENAME > /path/to/DATABASENAME_backup.sql
------------------------------------------------------------------------

Code (Text):

Have you backed up your databases ? [y/n] y

MariaDB 10.3.x https://mariadb.com/kb/en/mariadb/what-is-mariadb-102/

!!  Note  !!
upgrade process can take more >5 minutes.. you may want to shutdown
nginx server to not show mysql errors to visitors on your site or
put site(s) into maintenance mode before proceeding with mysql upgrade

Do you want to continue with upgrade to MariaDB 10.3.x ? [y/n] y

MariaDB 10.3.7 about to be installed

Code (Text):

*************************************************
MariaDB 10.3.x check available packages
yum -q list MariaDB-client MariaDB-common MariaDB-compat MariaDB-devel MariaDB-server MariaDB-shared --disablerepo=epel --disableplugin=priorities
*************************************************

Installed Packages
MariaDB-client.x86_64               10.2.15-1.el7.centos                @mariadb
MariaDB-common.x86_64               10.2.15-1.el7.centos                @mariadb
MariaDB-compat.x86_64               10.2.15-1.el7.centos                @mariadb
MariaDB-devel.x86_64                10.2.15-1.el7.centos                @mariadb
MariaDB-shared.x86_64               10.2.15-1.el7.centos                @mariadb
Available Packages
MariaDB-client.x86_64               10.3.7-1.el7.centos                 mariadb
MariaDB-common.x86_64               10.3.7-1.el7.centos                 mariadb
MariaDB-compat.x86_64               10.3.7-1.el7.centos                 mariadb
MariaDB-devel.x86_64                10.3.7-1.el7.centos                 mariadb
MariaDB-server.x86_64               10.3.7-1.el7.centos                 mariadb
MariaDB-shared.x86_64               10.3.7-1.el7.centos                 mariadb

Installing

Code (Text):

*************************************************
MariaDB 10.3.x YUM install...
yum -q -y install MariaDB-client MariaDB-common MariaDB-compat MariaDB-devel MariaDB-server MariaDB-shared --disablerepo=epel --disableplugin=priorities
*************************************************

Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
 * base: mirror.ventraip.net.au
 * extras: mirror.optus.net
 * rpmforge: mirror.ventraip.net.au
 * updates: mirror.optus.net
Resolving Dependencies
--> Running transaction check
---> Package MariaDB-client.x86_64 0:10.2.15-1.el7.centos will be updated
---> Package MariaDB-client.x86_64 0:10.3.7-1.el7.centos will be an update
---> Package MariaDB-common.x86_64 0:10.2.15-1.el7.centos will be updated
---> Package MariaDB-common.x86_64 0:10.3.7-1.el7.centos will be an update
---> Package MariaDB-compat.x86_64 0:10.2.15-1.el7.centos will be updated
---> Package MariaDB-compat.x86_64 0:10.3.7-1.el7.centos will be an update
---> Package MariaDB-devel.x86_64 0:10.2.15-1.el7.centos will be updated
---> Package MariaDB-devel.x86_64 0:10.3.7-1.el7.centos will be an update
---> Package MariaDB-server.x86_64 0:10.3.7-1.el7.centos will be installed
---> Package MariaDB-shared.x86_64 0:10.2.15-1.el7.centos will be updated
---> Package MariaDB-shared.x86_64 0:10.3.7-1.el7.centos will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package             Arch        Version                     Repository    Size
================================================================================
Installing:
 MariaDB-server      x86_64      10.3.7-1.el7.centos         mariadb      123 M
Updating:
 MariaDB-client      x86_64      10.3.7-1.el7.centos         mariadb       53 M
 MariaDB-common      x86_64      10.3.7-1.el7.centos         mariadb      157 k
 MariaDB-compat      x86_64      10.3.7-1.el7.centos         mariadb      2.8 M
 MariaDB-devel       x86_64      10.3.7-1.el7.centos         mariadb      7.1 M
 MariaDB-shared      x86_64      10.3.7-1.el7.centos         mariadb      395 k

Transaction Summary
================================================================================
Install  1 Package
Upgrade  5 Packages

Total download size: 186 M
Downloading packages:

MariaDB 10.3.7 official yum repo installed MySQL server

Code (Text):

mysqladmin ver
mysqladmin  Ver 9.1 Distrib 10.3.7-MariaDB, for Linux on x86_64
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Server version          10.3.7-MariaDB
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /var/lib/mysql/mysql.sock
Uptime:                 1 min 40 sec

Threads: 5  Questions: 404  Slow queries: 0  Opens: 186  Flush tables: 1  Open tables: 29  Queries per second avg: 4.040

Code (Text):

mysql -t -e "SELECT * FROM mysql.plugin;"
+---------------------------+------------------------+
| name                      | dl                     |
+---------------------------+------------------------+
| METADATA_LOCK_INFO        | metadata_lock_info.so  |
| QUERY_CACHE_INFO          | query_cache_info.so    |
| QUERY_RESPONSE_TIME       | query_response_time.so |
| QUERY_RESPONSE_TIME_AUDIT | query_response_time.so |
+---------------------------+------------------------+

Code (Text):

mysql -t -e "SHOW PLUGINS;"
+-------------------------------+----------+--------------------+------------------------+---------+
| Name                          | Status   | Type               | Library                | License |
+-------------------------------+----------+--------------------+------------------------+---------+
| binlog                        | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| mysql_native_password         | ACTIVE   | AUTHENTICATION     | NULL                   | GPL     |
| mysql_old_password            | ACTIVE   | AUTHENTICATION     | NULL                   | GPL     |
| wsrep                         | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| MRG_MyISAM                    | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| MEMORY                        | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| CSV                           | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| MyISAM                        | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| CLIENT_STATISTICS             | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INDEX_STATISTICS              | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| TABLE_STATISTICS              | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| USER_STATISTICS               | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| SQL_SEQUENCE                  | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| PERFORMANCE_SCHEMA            | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| InnoDB                        | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| INNODB_TRX                    | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_LOCKS                  | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_LOCK_WAITS             | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_CMP                    | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_CMP_RESET              | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_CMPMEM                 | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_CMPMEM_RESET           | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_CMP_PER_INDEX          | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_CMP_PER_INDEX_RESET    | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_BUFFER_PAGE            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_BUFFER_PAGE_LRU        | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_BUFFER_POOL_STATS      | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_METRICS                | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_FT_DEFAULT_STOPWORD    | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_FT_DELETED             | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_FT_BEING_DELETED       | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_FT_CONFIG              | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_FT_INDEX_CACHE         | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_FT_INDEX_TABLE         | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_TABLES             | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_TABLESTATS         | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_INDEXES            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_COLUMNS            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_FIELDS             | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_FOREIGN            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_FOREIGN_COLS       | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_TABLESPACES        | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_DATAFILES          | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_VIRTUAL            | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_MUTEXES                | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_SYS_SEMAPHORE_WAITS    | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| INNODB_TABLESPACES_ENCRYPTION | ACTIVE   | INFORMATION SCHEMA | NULL                   | BSD     |
| INNODB_TABLESPACES_SCRUBBING  | ACTIVE   | INFORMATION SCHEMA | NULL                   | BSD     |
| Aria                          | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| SEQUENCE                      | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| user_variables                | ACTIVE   | INFORMATION SCHEMA | NULL                   | GPL     |
| FEEDBACK                      | DISABLED | INFORMATION SCHEMA | NULL                   | GPL     |
| partition                     | ACTIVE   | STORAGE ENGINE     | NULL                   | GPL     |
| METADATA_LOCK_INFO            | ACTIVE   | INFORMATION SCHEMA | metadata_lock_info.so  | GPL     |
| QUERY_CACHE_INFO              | ACTIVE   | INFORMATION SCHEMA | query_cache_info.so    | BSD     |
| QUERY_RESPONSE_TIME           | ACTIVE   | INFORMATION SCHEMA | query_response_time.so | GPL     |
| QUERY_RESPONSE_TIME_AUDIT     | ACTIVE   | AUDIT              | query_response_time.so | GPL     |
+-------------------------------+----------+--------------------+------------------------+---------+

Code (Text):

mysql -t -e "SHOW ENGINES;"
+--------------------+---------+----------------------------------------------------------------------------------+--------------+------+------------+
| Engine             | Support | Comment                                                                          | Transactions | XA   | Savepoints |
+--------------------+---------+----------------------------------------------------------------------------------+--------------+------+------------+
| CSV                | YES     | CSV storage engine                                                               | NO           | NO   | NO         |
| MRG_MyISAM         | YES     | Collection of identical MyISAM tables                                            | NO           | NO   | NO         |
| MEMORY             | YES     | Hash based, stored in memory, useful for temporary tables                        | NO           | NO   | NO         |
| Aria               | YES     | Crash-safe tables with MyISAM heritage                                           | NO           | NO   | NO         |
| MyISAM             | YES     | MyISAM storage engine                                                            | NO           | NO   | NO         |
| PERFORMANCE_SCHEMA | YES     | Performance Schema                                                               | NO           | NO   | NO         |
| InnoDB             | DEFAULT | Supports transactions, row-level locking, foreign keys and encryption for tables | YES          | YES  | YES        |
| SEQUENCE           | YES     | Generated tables filled with sequential values                                   | YES          | NO   | YES        |
+--------------------+---------+----------------------------------------------------------------------------------+--------------+------+------------+

Interesting MariaDB 10.3 RPMs for CentOS 7 seem to build against older OpenSSL 1.0.1e instead of CentOS 7's OpenSSL 1.0.2 versions

Code (Text):

mysqladmin var | tr -s ' ' | grep version_ssl
| version_ssl_library | OpenSSL 1.0.1e-fips 11 Feb 2013 |

eva2000 · May 28, 2018

Interesting regarding Spider engine Spider Storage Engine Overview

The Spider storage engine is a storage engine with built-in sharding features. It supports partitioning and xa transactions, and allows tables of different MariaDB instances to be handled as if they were on the same instance. It refers to one possible implementation of ISO/IEC 9075-9:2008 SQL/MED.

When a table is created with the Spider storage engine, the table links to the table on a remote server. The remote table can be of any storage engine. The table link is concretely achieved by the establishment of the connection from a local MariaDB server to a remote MariaDB server.

When more than one Spider storage engine table can be used by the same connection, the connection is shared.

The Spider documentation on the MariaDB Knowledge Base is currently incomplete. See the Spider website for more: SpiderForMySQL.com, as well as the spider-1.0-doc and spider-2.0-doc repositories.
Click to expand...

Seems Spider engine like Haproxy would help scale in terms of concurrency/number of threads as expected but MariaDB already has thread pools feature which should do the same. Been using MariaDB thread pools myself for years now ever since they added the feature And Haproxy is on Centmin Mod to do list

Without connection pool or MariaDB thread pool, HaProxy and Spider have been protecting the tcp socket overflow without specific TCP tuning. In reality with a well tuned TCP stack or thread pool the curve should not decrease so abruptly to 0. Refer to the MariaDB Thread Pool to explore this feature.
Click to expand...

eva2000 · May 28, 2018

MariaDB blog has a few articles covering new MariaDB 10.3 features

Automatic Data Versioning in MariaDB Server 10.3 | MariaDB

Now with System Versioned Tables - Announcing MariaDB Server 10.3 Second Beta | MariaDB

Sequences Support in MariaDB Server 10.3 | MariaDB

MyRocks Storage Engine in MariaDB is Now Release Candidate | MariaDB

Log in / Register

Forums

Want more timely Centmin Mod News Updates?

MariaDB MariaDB 10.3.7 GA Release !

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

.

Log in / Register

Useful Searches

Want more timely Centmin Mod News Updates?

MariaDB MariaDB 10.3.7 GA Release !

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

.