Hybrid replication, i.e. combining Galera and asynchronous MySQL replication in the same setup, became much easier since GTID got introduced in MySQL 5.6. Although it was fairly straightforward to replicate from a standalone MySQL server to a Galera Cluster, doing it the other way round (Galera → standalone MySQL) was a bit more challenging. At least until the arrival of GTID.

There are a few good reasons to attach an asynchronous slave to a Galera Cluster. For one, long-running reporting/OLAP type queries on a Galera node might slow down an entire cluster, if the reporting load is so intensive that the node has to spend considerable effort coping with it. So reporting queries can be sent to a standalone server, effectively isolating Galera from the reporting load. In a belts and suspenders approach, an asynchronous slave can also serve as a …

We have been working on bringing out a build of MyRocks with Percona Server for MySQL.

MyRocks is a RocksDB-based storage engine. You can find more information about MyRocks here.

While there is still a lot of work to do, I want to share an experimental build of Percona Server for MySQL with MyRocks, which you can use to evaluate and test this engine

(WARNING: in NO WAY is this build supposed to be for production usage! Consider this ALPHA quality.)

The tar.gz binaries are available from our …

In a previous post I wrote about how read/write split is implemented in ProxySQL, and what I believe is the best practice for read/write split on top of MySQL servers:

• start sending all traffic to MySQL master
• identify what queries can be routed to the MySQL slaves
• create rules to route these queries

I believe I am remarking that in ProxySQL read/write split is a special case of query routing.
ProxySQL doesn't try to magically perform read/write split for every use case scenarios, but instead it gives you the tools and the power to route traffic dynamically, on demand, through a simple and powerful Admin interface.
It is a tool for DBAs that need to maintain a farm of MySQL servers, and guarantee uptime, high availability, and performance.

In this blog post I will present a use case on how …

In this blog, we’ll look at the

mysqlpump

 utility.

mysqlpump

 is a utility that performs logical backups (which means backing up your data as SQL statements instead of a raw copy of data files). It was added in MySQL Server version 5.7.8, and can be used to dump a database or a set of databases to a file and then loaded on another SQL server (not necessarily a MySQL server).

Its usage is similar to

mysqldump

, but it includes a new set of features. Many of the options are the same, but it was written from scratch to avoid being limited to

mysqldump

 compatibility. The Main Features Include:

• To make the dump process faster, it allows parallel processing of databases and objects within databases.
…

Once again, Pythian is organizing the traditional Open Source Database Community dinner in Santa Clara!

• When: Tuesday April 25, 7pm-10pm
• Where: David’s Restaurant, a short 5-minute walk from the Santa Clara Convention center.
• Tickets: Register here!

Among the attendees will be Pythian’s amazing lineup of speakers at the PerconaLive Conference.

This event is open to all open source database community members who will be in the area; many will be in town for the …

In MySQL 8.0.1, in addition to new as_cs collations (accent sensitive, case sensitive) for utf8mb4, we have also added a new collation for Japanese.

Introducing utf8mb4_ja_0900_as_cs

Collating rules for for Japanese are complex.  Japanese has multiple writing systems with katakana, hiragana, kanji, romaji.…

In a previous post I wrote about how read/write split is implemented in ProxySQL, and what I believe is the best practice for read/write split on top of MySQL servers:

• start sending all traffic to MySQL master
• identify what queries can be routed to the MySQL slaves
• create rules to route these queries

I believe I am remarking that in ProxySQL read/write split is a special case of query routing.
ProxySQL doesn't try to magically perform read/write split for every use case scenarios, but instead it gives you the tools and the power to route traffic dynamically, on demand, through a simple and powerful Admin interface.
It is a tool for DBAs that need to maintain a farm of MySQL servers, and guarantee uptime, high availability, and performance.

In this blog post I will present a use case on how …

In a week, me and some Booking.com colleagues will be in Santa Clara for Percona Live.

Booking.com is sponsoring the conference and we will be present at the Monday Evening Reception.  You do not need a tutorial pass to attend the dinner (even if it is on the tutorial day): any valid pass will do.  If you do not have your ticket yet, it is time to register (you can use the discount code “

While me and Fred were presenting Inexpensive Datamasking for MySQL with ProxySQL at FOSDEM 2017, we got a very interesting question: can ProxySQL be used to obfuscate backups obtained from mysqldump?
The short answer is yes!

Instead of dumping directly from MySQL Server, you can point mysqldump to ProxySQL that will perform the datamasking/obfuscation.
The dump file can then be used to provision new staging database without using production data, and follow compliance requirements.
This extremely simplify the "common" approach of dumping original data and storing it in an not obfuscated format (not good for compliance I believe), load the original data into a database, and finally perform some obfuscating query (that can really take a lot of time).

For this …

While me and Fred were presenting Inexpensive Datamasking for MySQL with ProxySQL at FOSDEM 2017, we got a very interesting question: can ProxySQL be used to obfuscate backups obtained from mysqldump?
The short answer is yes!

Instead of dumping directly from MySQL Server, you can point mysqldump to ProxySQL that will perform the datamasking/obfuscation.
The dump file can then be used to provision new staging database without using production data, and follow compliance requirements.
This extremely simplify the "common" approach of dumping original data and storing it in an not obfuscated format (not good for compliance I believe), load the original data into a database, and finally perform some obfuscating query (that can really take a lot of time).

For this …