We are pleased to announce the immediate availability of MariaDB 5.3.6. This stable (GA) release incorporates MySQL 5.1.62, some performance improvements, and several bug fixes.

Most importantly, MariaDB 5.3.6 includes a fix for a bug which, under certain rare circumstances, allowed a user to connect with an invalid password. This is a serious security issue. We recommend upgrading from older versions as soon as possible.

• MariaDB 5.3.6 Release Notes
• MariaDB 5.3.6 Changelog
• MariaDB 5.3.6 …

We are pleased to announce the immediate availability of MariaDB 5.1.62 and MariaDB 5.2.12. Both of these stable (GA) releases incorporate MySQL 5.1.62 and several bug fixes.

Most importantly, MariaDB 5.1.62 and 5.2.12 include a fix for a bug that under certain rare circumstances allowed a user to connect with an invalid password. This is a serious security issue. We recommend upgrading from older versions as soon as possible.

Please see the What is MariaDB 5.1 page for an overview of MariaDB 5.1, and the What is MariaDB …

Tungsten Replicator 2.0.5 was released this week-end. The release notes have quite a long list of bug fixes. Thanks to all the ones who have submitted bug reports, and fixes! There are a couple of new features as well. The replicator includes now a slave prefetch service. Unlike parallel replication, this feature works fine with a single database, and provides performance improvements that in many cases solve the slave lagging problems. This was a bitch of a feature to get right. Many have tried it, many have experienced various degrees of success, and several failures. We started with the bold assertiveness of the brave after an exciting talk at Percona Live in October, and I was …

Following closely on the heels of the MariaDB 5.3.4-rc release a couple of weeks ago, the MariaDB project is pleased to announce the immediate availability of MariaDB 5.3.5!

MariaDB 5.3.5 is the first stable (GA) release in the 5.3 series. Details and downloads are available from the following links:

• MariaDB 5.3.5 Release Notes
• MariaDB 5.3.5 Changelog
• MariaDB 5.3.5 Downloads

(Debian and Ubuntu packages are available from our mirrored apt repositories. A sources.list generator is available.)

About MariaDB 5.3

…

This is a major bugfix release. In addition to many important bugfixes, MySQL 5.5 patch sports a new feature: Rolling Schema Upgrade. Details in the download links.

Download here.

I am happy to announce the GA release of Flexviews. I've numbered the release 1.7.0 GA.
There are a small number of bug fixes and enhancements:

• 
  
• Fixes for views which have aggregate functions but no GROUP BY expressions could have had problems during incremental update.
  
• GA support for all aggregate functions except GROUP_CONCAT and AVG(distinct).
  
• The PERCENTILE_XX (ie PERCENTILE_90 for a 90th percentile calculation) is now stable too
  

FlexCDC got a number of fixes and improvements:

• 
  
• TIMESTAMP columns are now properly supported
  
• Now mysqlbinlog errors are detected, and the program exits gracefully
  
• FlexCDC now logs to a log file instead of writing to STDOUT/STDERR
  
• There are new PHP scripts for adding and removing table changelogs …

I am happy to announce the GA release of Flexviews. I've numbered the release 1.7.0 GA.
There are a small number of bug fixes and enhancements:

• 
  
• Fixes for views which have aggregate functions but no GROUP BY expressions could have had problems during incremental update.
  
• GA support for all aggregate functions except GROUP_CONCAT and AVG(distinct).
  
• The PERCENTILE_XX (ie PERCENTILE_90 for a 90th percentile calculation) is now stable too
  

FlexCDC got a number of fixes and improvements:

• 
  
• TIMESTAMP columns are now properly supported
  
• Now mysqlbinlog errors are detected, and the program exits gracefully
  
• FlexCDC now logs to a log file instead of writing to STDOUT/STDERR
  
• There are new PHP scripts for adding and removing table changelogs …

It's been long known that Galera optimistic replication and enterprise-size databases are a match made in heaven. Today we're going to get a little closer to testing this statement.
We'll have look at how Galera can scale out Sysbench OLTP complex 60 million rows workload in EC2. This is a first proper benchmark for 0.8 series and also the first benchmark of MariaDB/Galera port, so I'll start modest, just to see how it goes. I chose m1.large instances with 7.8Gb of RAM for server nodes and c1.xlarge instance for a client - I don't want the client to be a bottleneck.

For comparison I have also measured performance of a stock standalone MariaDB 5.1.55 server. I used the standard my.cnf that comes with MariaDB Debian package with the following alterations:

max_connections=1024
innodb_buffer_pool_size=6G
innodb_log_file_size=512M

Galera nodes also add

…

We’ve released Drizzle7! Not only that, we’re now calling it Generally Available – a GA release.

What does this mean? What does this GA label mean?

You could view as a GA label being “we’re pretty confident people aren’t going to on mass ask for our heads when they start using it”… which isn’t a too bad description. We also plan to maintain it, there could be future releases in this series that just include bug fixes – we won’t just immediately tell you to go and use the latest tarball or bzr tree. This release series is a good one to use.

Drizzle7 is something that can be packaged in Linux distros. It’s no longer something where the best bet is to add the PPA and upgrade every two weeks or build …

Percona Server version 5.1.55-12.6 is now available for download. It is now the current stable release version.

Changes

• Fixed compiler warnings in both the core server and in XtraDB. (Alxey Kopytov, Yasufumi Kinoshita)

Bugs Fixed

• Bug #602047 – The ROWS_READ columns of TABLE_STATISTICS and INDEX_STATISTICS were not properly updated when a query involved index lookups on an InnoDB table. (Yasufumi Kinoshita)
• Bug #707742 – The server could crash when trying to import a table which had not been previously prepared using xtrabackup --prepare --export. Also, on servers with huge buffer pools, adding or removing an index even on an empty InnoDB table could take a long time due to excessive locking when …