Changes & Improvements in MariaDB 10.2
- Implemented Features
- InnoDB as Default
- Syntax / General Features
- Incompatible Changes
- Replication / Binary Log
- GeoJSON / JSON
- Information Schema
- System Variables
- Status Variables
- Other Changes
- Comparison with MySQL
- List of All MariaDB 10.2 Releases
- See Also
MariaDB 10.2 is the previous major stable version. The first stable release was in May 2017, and it will be supported until May 2022.
The following lists the major new features in MariaDB 10.2:
InnoDB as Default
- InnoDB is now the default storage engine. Until MariaDB 10.1, MariaDB used the XtraDB storage engine as default. XtraDB in 10.2 is not up to date with the latest features of InnoDB and cannot be used. As the InnoDB on disk format is identical to XtraDB's this will not cause any problems when upgrading to MariaDB 10.2. See Why does MariaDB 10.2 use InnoDB instead of XtraDB?
Syntax / General Features
- MyRocks storage engine added. (It has its own maturity level. In MariaDB 10.2.14, it is considered Gamma) (MDEV-9658)
- Window functions have been introduced.
- The SHOW CREATE USER statement was introduced
- New CREATE USER options for limiting resource usage and tls/ssl
- New ALTER USER statement
- Non-recursive Common Table Expressions
- Recursive Common Table Expressions (MDEV-9864)
- New WITH statement.
WITHis a common table expression that allows you to refer to a subquery expression many times in a query (MDEV-8308 & MDEV-9864) — Original code from Galina Shalygina
- Support for CHECK CONSTRAINT (MDEV-7563)
- Support for DEFAULT with expressions (MDEV-10134)
- BLOB and TEXT fields can now have a DEFAULT value
- Lots of restrictions lifted for Virtual computed columns
- Number of supported decimals in DECIMAL has increased from
- Added catchall for list partitions (MDEV-8348)
- Oracle-style EXECUTE IMMEDIATE statement (MDEV-10585)
- PREPARE Statement/Dynamic SQL now understand most expressions (MDEV-10866, MDEV-10709).
- InnoDB tables now support spatial indexes
- ed25519 authentication plugin (MDEV-12160)
- Better InnoDB crash recovery progress reporting (MDEV-11027)
- Improvements to InnoDB startup/shutdown to make it more robust
- AWS Key Management plugin added for Windows, CentOS, RHEL, and Fedora packages
- Atomic writes support made more general. Shannon system SSD cards are now supported.
- TokuDB has been split into a separate package, mariadb-plugin-tokudb.
- SQL_MODE has been changed; in particular, NOT NULL fields with no default will no longer fall back to a dummy value for inserts which do not specify a value for that field.
- Replication from legacy MySQL servers may require setting binlog_checksum to NONE.
- New reserved words: OVER, RECURSIVE, and ROWS.
- Multiple triggers for the same event (MDEV-6112)
- The FOLLOWS/PRECEDES clauses have been added to the CREATE TRIGGER statement
- Multiple triggers are now counted in the Executed_triggers status variable (MDEV-10915)
- SHOW TRIGGERS and SHOW CREATE TRIGGER now include the date and time the trigger was created
Replication / Binary Log
- DML_only flashback can rollback instances/databases/tables to an old snapshot (MDEV-10570)
- New variable read_binlog_speed_limit permits restricting the speed at which the slave reads the binlog from the master (MDEV-11064) — Original code from Tencent Game DBA Team, developed by chouryzhou.
- Delayed replication is supported (MDEV-7145) — Backported from MySQL 5.6 by Kristian Nielsen funded by Booking.com.
- Compression of events in the binary log is supported (MDEV-11065) — Original code from Tencent Game DBA Team, developed by vinchen.
- Default binary log format changed to mixed (MDEV-7635)
- Default value of replicate_annotate_row_events changed to
- Default value of slave_net_timeout reduced to 60 seconds (MDEV-7635)
- Default server_id changed from
GeoJSON / JSON
- The JSON data type (an alias for LONGTEXT) was introduced.
- JSON functions added (MDEV-9143)
- Implement ST_AsGeoJSON and ST_GeomFromGeoJSON functions so the spatial features can be imported/exported using GeoJSON format (MDEV-11042)
- An information schema plugin to report all user variables, which creates the Information Schema USER_VARIABLES Table (MDEV-7331)
- Changes to the Information Schema COLUMNS table. Literals are now quoted in the
COLUMN_DEFAULTcolumn to distinguish them from expressions (MDEV-13132), and two new columns added providing information about generated (virtual, or computed) columns (MDEV-9255).
- EXPLAIN FORMAT=JSON now shows
outer_ref_conditionfield which contains the condition that the(?) SELECT checks on each re-execution (MDEV-9652)
- EXPLAN FORMAT=JSON now shows
sort_keyfield which shows the sort criteria used by
filesortoperation. (commit 2078392)
- EXPLAIN used to show incorrect information about how the optimizer resolved
ORDER BYclause or
Distinct. This was a long-standing problem with roots back in MySQL. Now, after MDEV-8646 and related fixes, the problem doesn't exist anymore. (For test cases, see MDEV-7982, MDEV-8857, MDEV-7885, MDEV-326)
- Connection setup was made faster by moving creation of THD to new thread (MDEV-6150)
- Pushdown conditions into non-mergeable views/derived tables (MDEV-9197, condition-pushdown-into-derived-table-optimization ) — Original code from Galina Shalygina
- ANALYZE TABLE has been re-implemented so as not to lock the entire table when collecting engine independent statistics (MDEV-7901)
- Internal CRC32 routines use the optimized implementation on Power8 — MDEV-9872
- Table cache can automatically partition itself as needed to reduce the contention (MDEV-10296)
- 88 new NO PAD collations added. In
NO PADcollations, end spaces are significant in comparisons (MDEV-9711) — Original code from Daniil Medvedev
- MariaDB now works when started with a MySQL 5.7.6+ data directory (MDEV-11170)
- Zipped File Tables for the CONNECT storage engine (MDEV-11295)
- The CONNECT engine now supports the JDBC Table type (MDEV-9765)
For a list of all new system variables, see System Variables Added in MariaDB 10.2. Variable changes include:
- New variable to disable deadlock detection innodb_deadlock_detect
- aria_recover has been renamed to aria_recover_options (MDEV-8542)
- Default values of the aria_recover and myisam_recover_options system variables changed to
- The server version can now be faked to work around dated applications that require a particular version string (MDEV-7780)
- slave_parallel_workers is now an alias for slave_parallel_threads
- New status variables com_alter_user, com_multi and com_show_create_user
- New variable for setting a directory for storing temporary non-tablespace InnoDB files, innodb_tmpdir
- New variable read_binlog_speed_limit permits restricting the speed at which the slave reads the binlog from the master (MDEV-11064)
- innodb_log_files_in_group can now be set to
- The thread pool now gives higher priority to connections that have an active transaction. This can be controlled with the new thread_pool_prio_kickup_timer and thread_pool_priority system variables. (MDEV-10297)
- Default value of group_concat_max_len changed to 1M (MDEV-7635)
- Default value of sql_mode changed to STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION (MDEV-7635) (MariaDB 10.2.4 and later)
- Default value of innodb_compression_algorithm changed to
zlib- this does not mean pages are now compressed by default, see compression (MDEV-11838)
- Default value of innodb_log_compressed_pages changed to
ONfrom MariaDB 10.1.2 to MariaDB 10.1.25 (MDEV-7635 and MDEV-13247)
- Default value of innodb_use_atomic_writes and innodb_use_trim changed to
- The unused innodb_api_* variables have been removed (MDEV-12050)
- tmp_disk_table_size was added to allow one to limit the size of temporary disk tables stored in tmpdir. At the same time tmp_memory_table_size was added an alias for tmp_table_size. At some point we plan to deprecate
tmp_table_size. (MariaDB 10.2.7 and later).
For a list of all new status variables, see Status Variables Added in MariaDB 10.2.
- Continuous binary log backup has been added to mysqlbinlog (MDEV-8713)
- mysql_zap and mysqlbug have been removed (MDEV-7376, MDEV-8654)
- Added support for OpenSSL 1.1 and LibreSSL (MDEV-10332)
- Persistent AUTO_INCREMENT for InnoDB (MDEV-6076)
- Support COM_RESET_CONNECTION (MDEV-10340)
- "fast mutexes" have been removed. These aren't faster than normal mutexes, and have been disabled by default for years (MDEV-8111)
- Old GPL client library is gone; now MariaDB Server comes with the LGPL Connector/C client library (MDEV-9055)
- MariaDB is no longer compiled with jemalloc
- TokuDB is now a separate package, not part of the server RPM (because TokuDB still needs jemalloc).
- Upgrading to a new major release no longer requires setting innodb_fast_shutdown to
0. Omitting it can make the upgrade process a lot faster. (MDEV-12289)
Comparison with MySQL
- Incompatibilities and Feature Differences Between MariaDB 10.2 and MySQL 5.7
- System Variable Differences Between MariaDB 10.2 and MySQL 5.7
- Function Differences Between MariaDB 10.2 and MySQL 5.7
- System Variable Differences Between MariaDB 10.2 and MySQL 5.6
- Function Differences Between MariaDB 10.2 and MySQL 5.6