MariaDB 10.0 is the development version of MariaDB. It is built on the MariaDB 5.5 series with backported features from MySQL 5.6 and entirely new features not found anywhere else.
This is the third 10.0-based release, and we are releasing it now to get it into the hands of any who might want to test it. …
MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. …
After some final testing and polishing, the MariaDB project and Codership are pleased to announce the release of MariaDB Galera Cluster 5.5.29. This is a Stable (GA) release. MariaDB Galera Cluster links:
MariaDB Galera Cluster is made for today’s cloud based environments. It is fully read-write scalable, comes with synchronous replication, allows multi-master topologies, and guarantees no lag or lost transactions. …
The MariaDB Java Client 1.1.1 has been released. You can download it here.
- Implement tcpAbortiveClose option, for “hard” socket close (CONJ-27)
- This option can be used in environments where connections are created and closed in rapid succession. Often, it is not possible to create a socket in such environment after a while, since all local “ephemeral” ports are used up by TCP connections in TCP_WAIT state.
The MariaDB project is pleased to announce the immediate availability of the following new stable (GA) MariaDB versions:
- MariaDB 5.5.29 — Release Notes, Changelog, Downloads
- MariaDB 5.3.12 — Release Notes, Changelog, Downloads
- MariaDB 5.2.14 — Release Notes, Changelog, Downloads
- MariaDB 5.1.67 — Release Notes, Changelog, Downloads
These releases are “bug fix” releases and they include, among other things, fixes for the following security vulnerabilities:
- A buffer overflow that can cause a server crash or arbitrary code execution (a variant of CVE-2012-5611)
- CVE-2012-5627/MDEV-3915 fast password brute-forcing using the “change user” command
- CVE-2012-5615/MDEV-3909 information leakage about existing user accounts via the protocol handshake
- fixes for DoS attacks – crashes and server lockups
- These releases of MariaDB also include all applicable upstream security fixes from MySQL, such as fix for a CVE-2012-5612/MDEV-3908 and other crashes.
The MariaDB Java Client 1.1.0 has been released. You can download it here.
This version focused on fixing all known database metadata bugs and ConnnectorJ incompatibilities. Specific fixes include:
- Consistent, compatible with ConnectorJ handling of JDBC catalogs vs schemas vs databases
- Implementation of several missing methods in DatabaseMetaData
- Better handling of statement timeouts
- OSGi-specific entries have been added to MANIFEST.MF so it can be used in OSGi environments
- Added support for dumpQueriesOnException=true in the JDBC URL
- Added support for IPv6 addresses in the connector
- Added SSL support
- and more…
The MariaDB project is pleased to announce the immediate availability of MariaDB 10.0.0! This is an alpha release.
MariaDB 10.0 is the current development version of MariaDB. It is built on the MariaDB 5.5 series with backported features from MySQL 5.6 and entirely new features not found anywhere else. See “Explanation on MariaDB 10.0” and “What comes in between MariaDB now and MySQL 5.6?” for more information on why we’re calling this series “MariaDB 10.0”.
This is the first 10.0-based release, and we are releasing it now to get it into the hands of any who might want to test it. …
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. …