MySQL 5.7 has a lot of enhancements and new features. I summarized this list previously in this blog post.
Adding replication filters online is one of the MySQL 5.7 features described in this manual. However, I will describe and summarize a few examples in this blog post.
Filtering replication events is also known as Partial Replication. Partial replication can be done from the master or slave. Filtering events on the master server via …
[Read more]MySQL 5.7 comes with built-in JSON support, comprising two major features:
Despite being added rather recently (in MySQL 5.7.8 to be precise
- one point release number before the 5.7.9 GA version), I feel
the JSON support so far looks rather useful. Improvements are
certainly possible, but compared to for example XML support
(added in 5.1 and 5.5), the JSON feature set added to 5.7.8 is
reasonably complete, coherent and standards-compliant.
(We can of course also phrase …
During the last few weeks I’ve been testing
and playing a bit with the new group-replication plugin available
for MySQL 5.7. Before continuing I’d like to clarify some
aspects: the plugin is only available in labs and is not yet
ready for production. The current version is 0.6. I used
5.7.9 GA running in a Vagrant 3 nodes cluster with CentOS
7.
As an additional note, I’ve tested previous version of plugin 0.5
against 5.7.8.rc and there are some good changes, so I recommend
starting with the GA version.
For the matter of my tests I’ve followed instructions from this post. It’s not as straightforward as it looks; there were some issues that needed to be handled, but I finally …
[Read more]MySQL 5.7 has been recently declared Generally Available and in it there is a set of new replication features. Over the last 6 years MySQL replication has evolved at a tremendous pace. MySQL 5.6 brought us a lot of new replication features, many that were ground breaking and yes, sometimes controversial.…
This week Oracle will release MySQL 5.7 GA, so
it’s a perfect time to do a quick review of the current state of
Percona Server 5.6.26, MySQL 5.6.26 and MySQL-5.7.8 RC. We used
two boxes from our benchmark lab for this:
– Box 1: 16 Cores+HT (32 virt cores)/fast PCIe ssd card/RAM:
192GB
– Box 2: 24 Cores+HT(48 virt cores)/fast PCIe ssd card/RAM: 128GB
Dataset: sysbench/uniform, 32 tables with 12M rows each,
~95GB
Tests: sysbench – point select, oltp read only, oltp
read/write
Test sequence: start server, warmup, series of the tests (each
lasts 5 minutes) from 1 to 4096 threads
Tests were run for two setups:
– CPU bound (in memory) – innodb_buffer_pool_size=100GB
– IO bound – innodb_buffer_pool_size=25GB
…
[Read more]When you have read my previous blog post about MariaDB 10.1 GA performance, you have probably wondered why I didn’t include any numbers for MySQL 5.7. There are two reasons: first MySQL wasn’t GA at that time and secondly MySQL is not running stable on Power8. Today I will come up with a comparison benchmark. […]
The post MariaDB 10.1 and MySQL 5.7 performance on commodity hardware appeared first on MariaDB.org.
Many years ago, I wrote about importing XML data into MySQL using
ExtractValue(). The reason I'm revisiting the
subject now is that I recently received an email request in
relation to my old blog post:
I came across one of your blogs on importing XML data to MySQL using ExtractData() and I am trying to do the same using MySQL (5.5) database. However, I am new to this kind of method and would like to seek your expertise on this.
I have an XML file that looks like this:
<?xml version="1.0" encoding="UTF-8"?> <wovoml xmlns="http://www.wovodat.org" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1.0" xsi:schemaLocation="http://www.wovodat.org phread2.xsd"> <Data> <Seismic> <SingleStationEventDataset> <SingleStationEvent code="VTAG_20160405000000" owner1="169" …[Read more]
Thanks to all who attended my webinar Introduction to MySQL SYS Schema. This blog is for me to address the extra questions I didn’t have time to answer on the stream.
Can i have the performance_schema enabled in 5.6 and then install the sys schema? Or they are one and the same?
You need to have enabled the performance_schema in order to use it through the sys schema. They are different entities. In general, performance_schema collects and stores the data, and sys schema reads and presents the data.
The installation of sys schema on primary database will be replicated to the slaves?
By default, no. If you wish that the Sys Schema replicates to the slaves, you can modify the before_setup.sql ( …
[Read more]
Percona Server 5.6.21+ and MySQL 5.7.8+ offer the super_read_only option that was first
implemented in WebscaleSQL. Unlike read_only, this
option prevents all users from running writes (even those with
the SUPER privilege). Sure enough, this is a great feature, but
what’s the relation with GTID? Read on!
TL;DR
Enabling super_read_only on all slaves when using
GTID replication makes your topology far less sensitive to errant
transactions. Failover is then easier and safer because creating
errant transactions is much harder.
GTID replication is awesome…
For years, all MySQL DBAs in the world have been fighting with positioning when working with replication. Each time you move a slave from one master to another, you must be very careful to start …
[Read more]Thank you for attending my July 22 webinar titled “Advanced Query Tuning in MySQL 5.6 and 5.7” (my slides and a replay available here). As promised here is the list of questions and my answers (thank you for your great questions).
Q: Here is the explain example:
mysql> explain extended select id, site_id from test_index_id where site_id=1
*************************** 1. row ***************************
id: 1
select_type: SIMPLE
table: test_index_id
type: ref
possible_keys: key_site_id
key: key_site_id
key_len: 5
ref: const
rows: 1
filtered: 100.00
Extra: Using where; Using index
why is site_id a covered index for the query, given the fact that a) we are selecting “id”, b) key_site_id only …
[Read more]