A stripped down version of TokuDB is running on MySQL 8.0.

mysql> select @@version\G; *************************** 1. row *************************** @@version: 8.0.0-dmr-debug 1 row in set (0.00 sec)
mysql> show create table test.t\G; *************************** 1. row ***************************        Table: t Create Table: CREATE TABLE `t` (   `id` int(11) NOT NULL,   PRIMARY KEY (`id`) ) ENGINE=TokuDB DEFAULT CHARSET=latin1 1 row in set (0.00 sec)
mysql> show engines\G; *************************** 6. row ***************************       Engine: TokuDB      Support: YES      Comment: Percona TokuDB Storage Engine with Fractal Tree(tm) Technology Transactions: YES           XA: YES   Savepoints: YES
mysql> create table test.t (id int primary key) engine=tokudb; Query OK, 0 rows affected (0.08 …

Today was the first day of sessions at Percona Live Europe 2016, and it was packed with exciting talks and important information on open source databases. Some of the most anticipated talks are those that cover what to expect in MySQL 8.0.

One of those talks was given by Oracle’s Manyi Lu, Director of Software Development. She discussed MySQL 8.0: what’s new in Optimizer.

In her talk, Manyi discussed what we could look forward to in MySQL 8.0’s optimizer. There are substantial improvements in the optimizer in MySQL 5.7 and MySQL 8.0. Most noticeably, users can now combine relational data with NoSQL using the new JSON features. MySQL also now supports functional indexes through generated columns. …

Percona announces the new release of Percona XtraDB Cluster 5.6.32-25.17 on October 4, 2016. Binaries are available from the downloads area or our software repositories.

Percona XtraDB Cluster 5.6.32-25.17 is now the current release, based on the following:

• Percona Server 5.6.32-78.1
• Galera Replication library 3.17
• Codership wsrep API version 25

Bugs Fixed:

• Fixed DONOR …

Overview

MySQL 8.0 comes with the new design of INFORMATION_SCHEMA subsystem. The blog MySQL 8.0: Improvements to Information_schema provides an overview of the improvements we made. This blog focuses mainly to demonstrate performance of the INFORMATION_SCHEMA in MySQL 8.0, giving us an idea on the kind of performance gain that one can expect.…

In the previous post, we looked into the basics of running MySQL containers on multiple Docker hosts managed by Swarm Mode, a native orchestration tool comes with Docker 1.12. However, at the time of writing, Docker Engine Swarm Mode does not support other networking plugins like Calico, Weave or Flannel. If we’d like to run any of these, we must run it outside of Docker Swarm mode and use other tools for orchestration e.g, Kubernetes, Mesos or Docker Swarm.

In this blog post, we are going to look into other networking drivers that support multi-host networking to best fit our MySQL setups. We are going to deploy MySQL Replication on top of three Docker hosts via Calico’s driver on multi-host networking. Weave and Flannel will be covered in the upcoming blog posts.

Calico …

In this blog post, we’ll look at MySQL 8.0 general tablespaces.

Introduction

MySQL 8.0 (the DMR version is available now) has two great features (among others):

1. The new data dictionary completely removed *.frm files, which is great
2. The ability to create a tablespace and assign a group of tables to it (originally introduced in 5.7).

With those two options, we can use MySQL for creating multi-tenant environments with a “schema per customer” approach.

Schema per Customer with MySQL 8.0

Using schema per customer with older MySQL versions presents issues  … namely the number of files. (I’ve described …

Here are the last details about the Percona Live 2016 Community Dinner hosted at Booking.com:

you can still register the menu is below the program of the lightning talks is on Giuseppe blog

Booking.com will also do a short talk.  The subject is a surprise !

If you are coming directly to the dinner (not via boats), please bring your registration ticket (electronic version ok) so you can access

The Percona Live Europe Open Source Database Conference 2016 in Amsterdam got off to a great start on Monday with a day of tutorials. One of the ones most anticipated was Become a MySQL DBA Part 1 and Part 2, given by Severalnines’ Johan Andersson (CTO) and Krzysztof Książek (Senior Support Engineer).

This hands-on tutorial is intended to help you navigate your way through the steps that lead to becoming a MySQL DBA. Johan and Krzysztof discussed the most important aspects of managing MySQL infrastructure, as well as shared best practices and tips on how to perform the most common activities.

They covered:

…

There are numerous ways to migrate into MySQL Fabric. Most of them require serious changes in your application - you have to switch to the MySQL Fabric connector to actually benefit from the MySQL Fabric infrastructure. You may also have to implement some kind of data-awareness in your application as it will have to pass a sharding key (some value from the column which is used to shard a given table) when connecting to MySQL Fabric. This process may be not possible to do in a single step, so we prepared a proof of concept to show you how to migrate without application changes.

The solution consists of several elements. At the backend, there’s MySQL Fabric with its sharding system of high availability groups and tools around it. Another layer is built using MySQL Router - it allows regular MySQL clients to connect to different high availability groups created in MySQL Fabric. It doesn’t solve the problem of routing queries to the correct …

If you use JSON UDFs in MySQL 5.6 there are a few things to consider before upgrading to MySQL 5.7. From a schema perspective, if you have JSON stored in text columns you can decide when to convert those columns to the new JSON datatype after you upgrade, but due to namespace collisions and format differences it's probably not safe to upgrade without dropping some or all of the existing UDFs and updating your queries that use those UDFs.

Read on for details...

Namespace collisions

There are 15 functions in JSON UDFs version 0.4.0. Nine of those names are used by native JSON functions in MySQL 5.7, so it's not possible to continue using those nine UDFs in MySQL 5.7. Therefore before you upgrade you should probably drop these UDFs:

DROP FUNCTION IF EXISTS json_append; DROP FUNCTION IF EXISTS json_depth; DROP FUNCTION IF EXISTS json_extract; DROP FUNCTION IF EXISTS json_merge; DROP FUNCTION IF EXISTS …