MariaDB MariaDB 10.0.18 Released

rdan · May 8, 2015

Changes
In addition to the MariaDB-5.5.43 fixes and improvements, the following fixes and improvements have been made toMariaDB 10.0.18.

Performance Schema updated to 5.6.24

XtraDB updated to XtraDB-5.6.23-72.1

Innodb updated to InnoDB-5.6.24

Spider updated to 3.2.21

Mroonga updated to 5.02

Parser

Fixed unrecognised column quoted with backticks in a function in a HAVING clause (MDEV-7301).

ALTER TABLE with conflicting CHARACTER SET and CONVERT TO CHARACTER SET arguments now reports error (MDEV-7386).

Fixed Regression (from 10.0.14): Bit and hex string literals changed column names (MDEV-7629).

Optimizer

Merged derived tables/VIEWs incorrectly increment created_tmp_tables (MDEV-7586).

TODO - Stalled - Assertion in subselects in queries run twice in the same connection (MDEV-7445).

Alter Table

Some symbols in table name can cause to Error Code: 1050 when created FK. Table name is on filename charset but foreign key identifiers are not. This lead incorrect foreign key identifier number to be used (MDEV-7627).

ALTER [ONLINE] TABLE with no options no longer requires a table copy (MDEV-7390).

Fixed a case where it was impossible to create copy of a table if the table contained a default value for timestamp field in sql_mode="NO_ZERO_DATE" (MDEV-7778).

Other SQL Commands

INSTALL PLUGIN can now be done in bootstrap mode where authentication is disabled (MDEV-7781).

Corrected error handing in AES_ENCRYPT/AES_DECRYPT where incorrect data could result in a SSL client connection being terminated (MDEV-7697).

Corrected Assertion `status_var.memory_used == 0' failed in THD::THD() on disconnect after executing EXPLAIN for multi-table UPDATE (MDEV-7038).

Fixed crash when dropping user within rebuild_role_grants which occurs in some cases in SHOW GRANTS andDROP ROLE (MDEV-7774).

SHOW GRANTS now shows the password for users that have the password field set, auth_string field empty, plugin=mysql_native_password (MDEV-7985).

Innodb

In Debug builds, an assertion could be triggered on really large blobs (MDEV-7754).

Fixed segfault when a virtual column used on an Innodb table and an index was created on a field after the virtual column (MDEV-7367).

Fixed server crash when inserting more rows than available space on disk (MDEV-7685).

Now possible to get Innodb internal primary key for wrapper type storage engines (MDEV-7714).

Replication

Starting with this release, commits in certain instances in parallel replication complete immediately, avoiding losing throughput when many transactions need conflicting locks. See binlog_commit_wait_count (MDEV-7847 / MDEV-7882).

Fixed parallel replication worker threads that hung in some cases with non-transactional event groups (MDEV-7929).

Fixed parallel replication error where deadlock was incorrectly handled (MDEV-8031).

Fixed replication aborting on DROP /*!40005 TEMPORARY */ TABLE IF EXISTS (MDEV-8016).

Fixed replication of temporary tables in statement mode that are grouped - fix MDEV-7668 wasn't sufficient (MDEV-7936).

Fixed ANALYZE TABLE which was ordered incorrectly in the binlog (MDEV-7888).

Added more detailed information about errors when GTID mode IO threads fail to connect (MDEV-7975).

Fixed temporary tables lost at STOP SLAVE in GTID mode if master has not rotated binlog since restart (MDEV-6403).

Fixed incorrect relay log start position when restarting SQL thread after error in parallel replication (MDEV-6589).

Fixed problem where slave was 10x slower to execute a set of statements compared to the master when using RBR (MDEV-7578).

Parallel replication worker threads are not spawned until needed (when an SQL thread is started), and they will be de-spawned if all SQL threads are stopped (MDEV-5289).

Multilevel slaves with parallel replication - better logic resulted in performance increase to group more transactions at the first slave level resulting in increased parallelism at the second replication level (MDEV-7249).

Fixed problem where Intermediate master groups using CREATE TEMPORARY TABLE with INSERT could cause the INSERT to occur before the TEMPORARY TABLE it operates on, causing parallel replication failure (MDEV-7668).

Slave SQL: stopping replication on a non-last RBR event with annotations no longer results in segfaults (MDEV-7864).

MASTER_POS_WAIT(log_name,log_pos,timeout,"connection_name") when connection name is specified now respects the timeout (MDEV-7130).

New status variables binlog_group_commit_trigger_count, binlog_group_commit_trigger_timeout, andbinlog_group_commit_trigger_lock_wait used to examine which triggers caused a group commit to be made (MDEV-7802).

Fixed seconds_behind_master display in SHOW SLAVE STATUS which occasionally returned 0 when it really was much higher (MDEV-5114).

Platforms

PowerPC - fixed Innodb locking issue under high load - (MDEV-7148).

BigEndian now builds in Cassandra storage engine (MDEV-7839).

Fixed crash when running MariaDB Debug with InnoDB on Windows (MDEV-8079).

Connect Engine

CONNECT Engine Column names are now retrieved properly when field values are not latin1 characters (MDEV-7521).

Fixed problem where connecting to missing remote table caused error that was re-reported when SHOW TABLE STATUS on a correctly formed table (MDEV-7636).

Fixed problem where CONNECT returned error 174 on query to MS SQL Server 2012 involving timestamp column when the condition is given as a date literal (MDEV-7840).

CONNECT now works with if(exists(select * from test)) statement in procedures (MDEV-7852).

Fixed user variable assignment with SET @var = that resulted in ERROR 1148 (42000): CONNECT Unsupported command (MDEV-7616).

Removed assertion in delete_or_rename_table that caused crashes on (XML) HTML tables (MDEV-7935).

Added UDF Json_Array_Delete (MDEV-7935).

Fixed a problem where defining indexes on a connect engine caused wrong results (MDEV-8090).

OQ Graph Engine

Fixed issue with incorrect handling of multiple threads (MDEV-6282, MDEV-6345 and MDEV-6784).

Other

SSL connections increased from 512 to 1024 bits in Diffie-Hellman exchange to support fips (MDEV-7794).

Fixed problem where SSL read/write timeouts were 1000 times too high due to seconds/milliseconds error (MDEV-8096).

OpenSSL now uses MD5 even if FIPS prohibited it, fixing a previous crash. This is fine as MD5 is not used for cryptographical purposes (md5 is used internally for P_S message digests and for view checksums) (MDEV-7788).

Fixed problem where Initialization of status variables was not invoked for embedded (no bug reference. code change)

Corrected wrong results with bigint when compiled with gcc 5.0 (MDEV-7973).

Fixed assertion in Protocol::end_statement where CREATE VIEW occured after another connection aborted (MDEV-8045).

Client

Fixed MariaDB client where it could hang in an infinite loop based on no IO data returned (MDEV-8014).

Security Fixes

Fixes for the following security vulnerabilities:

CVE-2014-8964 bundled PCRE contained heap-based buffer overflow vulnerability that allowed the server to crash or have other unspecified impact via a crafted regular expression made possible with theREGEXP_SUBSTR function (MDEV-8006).

CVE-2015-0501

CVE-2015-2571

CVE-2015-0505

CVE-2015-0499

New and Deprecated Distributions
As per the MariaDB Deprecation Policy, this will be the final release of MariaDB 10.0 for Fedora 19 "Schrödinger's Cat", Ubuntu 10.04 LTS "Lucid", Mint 9 LTS "Isadora", and Debian 6 "Squeeze". When the next version of MariaDB 10.0 is released, repositories for these distributions will go away.

We have also added a couple of new Linux distributions with this release. Both Fedora 21 and Ubuntu 15.04 "Vivid" repositories are now available. As this is the first release with these repositories, they are considered experimental. Please let us know if you run into any issues with them.

For a complete list of changes made in MariaDB 10.0.18, with links to detailed information on each push, see thechangelog.

More Info: MariaDB 10.0.18 Release Notes - MariaDB Knowledge Base

eva2000 · May 8, 2015

wow that's a substantial change and bug fix list

sepulchre · May 9, 2015

How can I update to the latest MariaDB?

Code:

   MariaDB MySQL Upgrade Sub-Menu            
--------------------------------------------------------
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). Back to Main menu
--------------------------------------------------------
Enter option [ 1 - 4 ]

I don't see any option to upgrade MariaDB 10.x.

eva2000 · May 9, 2015

MariaDB is simple yum update command

list available updates

Code:

yum list updates -q
Updated Packages
MariaDB-client.x86_64                                          10.0.18-1.el7.centos                                    mariadb
MariaDB-common.x86_64                                          10.0.18-1.el7.centos                                    mariadb
MariaDB-compat.x86_64                                          10.0.18-1.el7.centos                                    mariadb
MariaDB-devel.x86_64                                           10.0.18-1.el7.centos                                    mariadb
MariaDB-server.x86_64                                          10.0.18-1.el7.centos                                    mariadb
MariaDB-shared.x86_64                                          10.0.18-1.el7.centos                                    mariadb

yum update

Code:

yum -y update

Code:

 yum -y update
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
 * base: centos.mirrors.hoobly.com
 * epel: mirrors.kernel.org
 * extras: mirrors.kernel.org
 * rpmforge: mirror.hmc.edu
 * updates: mirror.pac-12.org
148 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package MariaDB-client.x86_64 0:10.0.17-1.el7.centos will be updated
---> Package MariaDB-client.x86_64 0:10.0.18-1.el7.centos will be an update
---> Package MariaDB-common.x86_64 0:10.0.17-1.el7.centos will be updated
---> Package MariaDB-common.x86_64 0:10.0.18-1.el7.centos will be an update
---> Package MariaDB-compat.x86_64 0:10.0.17-1.el7.centos will be updated
---> Package MariaDB-compat.x86_64 0:10.0.18-1.el7.centos will be an update
---> Package MariaDB-devel.x86_64 0:10.0.17-1.el7.centos will be updated
---> Package MariaDB-devel.x86_64 0:10.0.18-1.el7.centos will be an update
---> Package MariaDB-server.x86_64 0:10.0.17-1.el7.centos will be updated
---> Package MariaDB-server.x86_64 0:10.0.18-1.el7.centos will be an update
---> Package MariaDB-shared.x86_64 0:10.0.17-1.el7.centos will be updated
---> Package MariaDB-shared.x86_64 0:10.0.18-1.el7.centos will be an update
--> Finished Dependency Resolution

Dependencies Resolved

===============================================================================================================================
 Package                         Arch                    Version                                Repository                Size
===============================================================================================================================
Updating:
 MariaDB-client                  x86_64                  10.0.18-1.el7.centos                   mariadb                   10 M
 MariaDB-common                  x86_64                  10.0.18-1.el7.centos                   mariadb                   23 k
 MariaDB-compat                  x86_64                  10.0.18-1.el7.centos                   mariadb                  1.4 M
 MariaDB-devel                   x86_64                  10.0.18-1.el7.centos                   mariadb                  6.3 M
 MariaDB-server                  x86_64                  10.0.18-1.el7.centos                   mariadb                   54 M
 MariaDB-shared                  x86_64                  10.0.18-1.el7.centos                   mariadb                  1.2 M

Transaction Summary
===============================================================================================================================
Upgrade  6 Packages

Total size: 73 M
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Updating   : MariaDB-common-10.0.18-1.el7.centos.x86_64                                                                 1/12 
  Updating   : MariaDB-client-10.0.18-1.el7.centos.x86_64                                                                 2/12 
  Updating   : MariaDB-server-10.0.18-1.el7.centos.x86_64                                                                 3/12 
  Updating   : MariaDB-compat-10.0.18-1.el7.centos.x86_64                                                                 4/12 
  Updating   : MariaDB-shared-10.0.18-1.el7.centos.x86_64                                                                 5/12 
  Updating   : MariaDB-devel-10.0.18-1.el7.centos.x86_64                                                                  6/12 
  Cleanup    : MariaDB-server-10.0.17-1.el7.centos.x86_64                                                                 7/12 
Shutting down MySQL.. SUCCESS! 
Starting MySQL. SUCCESS! 
  Cleanup    : MariaDB-devel-10.0.17-1.el7.centos.x86_64                                                                  8/12 
  Cleanup    : MariaDB-client-10.0.17-1.el7.centos.x86_64                                                                 9/12 
  Cleanup    : MariaDB-shared-10.0.17-1.el7.centos.x86_64                                                                10/12 
  Cleanup    : MariaDB-compat-10.0.17-1.el7.centos.x86_64                                                                11/12 
  Cleanup    : MariaDB-common-10.0.17-1.el7.centos.x86_64                                                                12/12 
  Verifying  : MariaDB-compat-10.0.18-1.el7.centos.x86_64                                                                 1/12 
  Verifying  : MariaDB-server-10.0.18-1.el7.centos.x86_64                                                                 2/12 
  Verifying  : MariaDB-shared-10.0.18-1.el7.centos.x86_64                                                                 3/12 
  Verifying  : MariaDB-common-10.0.18-1.el7.centos.x86_64                                                                 4/12 
  Verifying  : MariaDB-client-10.0.18-1.el7.centos.x86_64                                                                 5/12 
  Verifying  : MariaDB-devel-10.0.18-1.el7.centos.x86_64                                                                  6/12 
  Verifying  : MariaDB-common-10.0.17-1.el7.centos.x86_64                                                                 7/12 
  Verifying  : MariaDB-shared-10.0.17-1.el7.centos.x86_64                                                                 8/12 
  Verifying  : MariaDB-server-10.0.17-1.el7.centos.x86_64                                                                 9/12 
  Verifying  : MariaDB-compat-10.0.17-1.el7.centos.x86_64                                                                10/12 
  Verifying  : MariaDB-devel-10.0.17-1.el7.centos.x86_64                                                                 11/12 
  Verifying  : MariaDB-client-10.0.17-1.el7.centos.x86_64                                                                12/12 

Updated:
  MariaDB-client.x86_64 0:10.0.18-1.el7.centos                   MariaDB-common.x86_64 0:10.0.18-1.el7.centos                  
  MariaDB-compat.x86_64 0:10.0.18-1.el7.centos                   MariaDB-devel.x86_64 0:10.0.18-1.el7.centos                  
  MariaDB-server.x86_64 0:10.0.18-1.el7.centos                   MariaDB-shared.x86_64 0:10.0.18-1.el7.centos                  

Complete!

sepulchre · May 9, 2015

Thanks.
For me there were no yum update packages available. I assume the automatically yum update setting took care of that. Checked the version in phpmyadmin and it was already 10.0.18.

One question though, why is the approach for updating MariaDB different than to nginx or php?
I mean when I want to upgrade nginx or php version, I simply go to my centmin menu but for MariaDB it is not the case.

eva2000 · May 9, 2015

MariaDB is more complex with many moving pieces and requires stability and reliability so install and upgrades are best left to yum package install instead of source compilation. The Centmin Mod shell menu is mainly reserved for source related compilation functions or to simplify very complex tasks like major version upgrades for MariaDB 5.2 to 5.5 to 10.0

Minor upgrades of MariaDB are much easier via yum upgrade command

rdan · May 9, 2015

The MariaDB project is pleased to announce the immediate availability
of MariaDB 10.0.19. This is a Stable (GA) release. See the Release
Notes and Changelog for details.

- - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

MariaDB 10.0.19
- Release Notes: MariaDB 10.0.19 Release Notes - MariaDB Knowledge Base
- Changelog: MariaDB 10.0.19 Changelog - MariaDB Knowledge Base
- Downloads: MariaDB 10.0.19 Stable - MariaDB

Changes

Fixed the server crash caused by mysql_upgrade (MDEV-8115)

sepulchre · May 9, 2015

@eva2000
Thanks for explaining. I understand, it makes sense.

Just, you could still integrate it in the centmin menu, like:
Code:
   MariaDB MySQL Upgrade Sub-Menu           
--------------------------------------------------------
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 10.x YUM upgrade
5). Back to Main menu
--------------------------------------------------------
Enter option [ 1 - 5 ] 
And when we choose 4.) it will then do a "yum -y update".
I know, it is actually not much handier, but just for the purpose of that everything related to the LEMP is in one menu.

I know we had this discussion already. We have to learn basic commands, just me as a noob find it always very odd, that some of upgrades like nginx, php, etc. I have to call the menu, but some other things like MariaDB or Centmin branch update I have to do via direct command lines. It is not foolproof in some way.
Anyway, I don't want to start a debate about this. You are the pro, you know the best. I totally accept any way you choose. I am just trying to give a feedback.

Thanks for explaining, have a nice day.

eva2000 · May 9, 2015

some things will always be SSH command line as it's basically faster to do than via ssh centmin.sh menu and can be automated if you use yum-cron auto updates

thanks for feedback though

quicksalad · Jun 4, 2015

I'm trying to update MariaDB10, but I'm not getting version on the list.

It only says:
MariaDB-client.i686 5.5.43-1.el6

eva2000 · Jun 4, 2015

quicksalad said: ↑

I'm trying to update MariaDB10, but I'm not getting version on the list.

It only says:
MariaDB-client.i686 5.5.43-1.el6
Click to expand...

which submenu option you running ? for 5.5 to 10 it's submenu option 3 but you need to edit a variable as per MariaDB - MariaDB 5.5 to 10 upgrade beta testing | Centmin Mod Community for inc/mariadb_submenu.inc file and change variable ENABLE_MARIADBTENUPGRADE='n' to ENABLE_MARIADBTENUPGRADE='y'. Save file. Full details MariaDB - MariaDB 5.5 to 10 upgrade beta testing | Centmin Mod Community

quicksalad · Jun 4, 2015

smooth and sweet... thanks

re-login and now it's updated...

Log in / Register

Forums

Join the community today

MariaDB MariaDB 10.0.18 Released

rdan Well-Known Member

eva2000 Administrator Staff Member

sepulchre Member

eva2000 Administrator Staff Member

sepulchre Member

eva2000 Administrator Staff Member

rdan Well-Known Member

sepulchre Member

eva2000 Administrator Staff Member

quicksalad Member

eva2000 Administrator Staff Member

quicksalad Member

.

Log in / Register

Useful Searches

Join the community today

MariaDB MariaDB 10.0.18 Released

rdan Well-Known Member

eva2000 Administrator Staff Member

sepulchre Member

eva2000 Administrator Staff Member

sepulchre Member

eva2000 Administrator Staff Member

rdan Well-Known Member

sepulchre Member

eva2000 Administrator Staff Member

quicksalad Member

eva2000 Administrator Staff Member

quicksalad Member

.