The long awaited first release candidate of MySQL 8.0 is now available. The theme of this release is
“making MySQL better for modern apps”. What does that mean exactly?
A modern application is mobile first. Mobile-first is not just a theme applied to an existing app, it is about using context about the user (such as their location) and reducing the clicks required for a transaction.
In MySQL 8.0, we will be introducing a new configuration parameter called
innodb_dedicated_server=bool. When ON, this option will look at the system memory, and then automatically set the these configuration parameters using the following rules:
Rene wrote on the ProxySQL blog yesterday:
Although MySQL Query Cache was meant to improve performance, it has serious scalability issues and it can easily become a severe bottleneck.
This is indeed something we have observed in the MySQL team for a while.…
Long time MySQL users will recognize that there are two varieties of utf8 support in MySQL;
utf8mb3 and utf8mb4. Let me dig a little bit deeper in explaining the history between the two:
MySQL 4.1 (2004) was the first version to support character sets and collations.
In MySQL 5.7, one of the most popular new features is the introduction of JSON:
JSON data type A
set of 20 functions to search, manipulate and create JSON documents
Virtual Columns for JSON indexing
In MySQL 8.0 we plan to extend this functionality (for example: with the addition of
JSON aggregate functions), but we are also considering changing the behaviour of one of the existing functions.…
In the MySQL team, one of our focuses over the last few releases has been improving the usability of the MySQL Server for operations teams. The results can be seen in a number of areas:
Our continued investment in Performance Schema.
Starting with MySQL 8.0, we will drop
libmysqld (aka “embedded server”). This change will affect only a handful of users, but for context let me start with an introduction. Introduction
libmysqld (also referred to as “the embedded server”) is a way of using MySQL without the client server protocol.…
The MySQL Engineering Team at their BOF session on Tuesday night. Sunny Bains in focus answering InnoDB questions.
On behalf of the entire team, I would like to thank you for stopping by our “
meet the MySQL engineering team” BOF held Tuesday night.…
A number of members of the MySQL Engineering Team will be at Percona Live and the MySQL Innovation Day over the next week or so. Here is where you can find us:
Tuesday 19 April 2016
Wednesday 20 April 2016
Thursday 21 April
Monday 25 April
We’ll all be present at the
MySQL Innovation Day.…
Starting with MySQL 5.7,
performance_schema has been enhanced to instrument metadata locks, and can be turned on by adding the following line to your my.cnf file:
performance - schema - instrument = 'wait/lock/metadata/sql/%=ON'
(At runtime, it can also be enabled by modifying the setup_instruments table in performance_schema.)
From here, you can now query
performance_schema.metadata_locks to reveal all currently open metadata locks on your server: