Tag Archives: MariaDB
Like others we were not satisfied with the fix for a bug in MySQL which caused the query cache and partitioning to not work reliably together. The bug, in simple terms, was that if the query cache was enabled and you used partitioned tables and if a partitioned table was using a transactional engine like InnoDB or XtraDB, the query cache could, under certain circumstances, return incorrect results.
Returning incorrect results is a definite, high-priority bug. However, the upstream fix was to disable all caching of queries from partitioned tables. We wanted a better solution because the query cache can be very useful and beneficial for partitioned tables, just like it is useful and beneficial for non-partitioned tables. …
It is not a secret that we’ve been kicking the tires and playing with JIRA for project management. After using it since the beginning of the year most of us like the feel of it and we’ve decided that it makes sense to start using it more.
As you know, the MariaDB project has many fragmented resources. We report bugs in Launchpad. We store our plans in worklog. We’ve never used the Launchpad Blueprint feature for this very reason. We don’t use Launchpad Answers because we have the Knowledgebase.
With this move to hosted JIRA (yes, this is an important link: https://mariadb.org/jira) we can report bugs, have future plans, and also give users a roadmap which is pretty cool. …
Over the past few days extensive conversations around a new security vulnerability in MariaDB and MySQL have taken place.
It all started as a chain reaction when Monty Program publicly disclosed information about the flaw they had found and about how to make sure your MariaDB and MySQL installations can be fixed. The initial information got assigned the security vulnerabitlity identifier CVE-2012-2122 and the contents can be seen e.g. here http://seclists.org/oss-sec/2012/q2/493.
The bug was found two months ago on April 4th.
Before disclosing the information publicly, given the seriousness of this bug and considering the millions of MySQL and MariaDB installations deployed worldwide, Monty Program informed the biggest distributors of MySQL and MariaDB as a precaution. …
We’re quite happy that we’ve released four major releases that are production ready (better known as generally available or GA in the MySQL world) in the last 26 months. That is just a little over two years, and a whole lot of features. In that same time, MySQL has seen one GA release (MySQL 5.5) and we’re all eagerly awaiting the upcoming MySQL 5.6.
You’ll note that we built MariaDB 5.1, 5.2, and 5.3 based on the MySQL 5.1 codebase. A significant number of features went into MariaDB 5.3 (our biggest GA release to date), with the biggest changes in the optimizer in over a decade. …
Continue reading “What comes in between MariaDB now and MySQL 5.6?”
On Friday last week, after the intensive days of the conference, Ars Technica wrote and published a nice article about MariaDB including many of the messages we had been delivering during the conference, http://arstechnica.com/business/news/2012/04/mysql-founders-latest-mariadb-release-takes-enterprise-features-open-source.ars.
Last year, when it became clear that O’Reilly wasn’t going to arrange the MySQL user conference in the future, there was a lot of discussion on who should arrange it. In the end Percona was pretty fast informing everyone that they had booked the convention center in Santa Clara to arrange the conference this year. …
Continue reading “MariaDB at the MySQL Conference & Expo 2012”
We are pleased to announce the immediate availability of MariaDB 5.5.23. This stable (GA) release incorporates MariaDB 5.3.6 and MySQL 5.5.23, some performance improvements, and bug fixes.
Please see the What is MariaDB 5.5 page for an overview of MariaDB 5.5.
Sources, binaries, and package downloads are available from our network of MariaDB mirrors. Debian and Ubuntu packages are available from our mirrored apt repositories. We have a sources.list generator for creating sources.list entries. …
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.
Please see the What is MariaDB 5.3 page for an overview of MariaDB 5.3. …
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 5.2 page for an overview of MariaDB 5.2. …