Percona announces the release of Percona Monitoring and Management 1.2.1 on August 16, 2017.
For install and upgrade instructions, see Deploying Percona Monitoring and Management.
This hotfix release improves memory consumption.
Changes in PMM Server
We’ve introduced the following changes in PMM Server 1.2.1:
Bug fixes
PMM-1280: PMM server affected by nGinx CVE-2017-7529. An …
Actually, Mysqlbinlog tools can’t miner mysql binlog exactly correct.
In this post ,a special environment we got may hexadecimal characters what we don’t need.
Read this PDF: Special-code-rollback.pdf
TL;DR: unless you know what you are doing, you should always have a primary key on your tables when replicating in RBR (and maybe even all the time).
TL;DR2: MariaDB 10.1 has an interesting way to protect against missing a primary key (innodb_force_primary_key) but it could be improved.
A few weeks ago, I was called off hours because replication delay on all the slaves from a replication chain
Join Percona’s, Technical Services Manager, Jervin Real as he presents Lock, Stock and Backup: Data Guaranteed on Wednesday, August 16, 2017 at 7:00 am PDT / 10:00 am EDT (UTC-7).
Backups are crucial in a world where data is digital and uptime is revenue. Environments are no longer bound to traditional data centers, and span multiple cloud providers and many heterogeneous environments. We need bulletproof backups and impeccable recovery processes. This talk aims to answer …
[Read more]In the quest to secure MySQL as well as ease the number of complicated passwords to remember, many organizations are looking into external authentication, especially using LDAP. For free and open source, Percona’s PAM authentication plugin is the standard option.
tl;dr is I go through how to compile php-cli for use with auth_pam plugin.
Background
There are two plugins that can be used. From the documentation, the two plugins are:
Replication in MySQL has been around for a long time, and has been steadily improving over the years. It has been more like evolution rather than revolution. This is perfectly understandable, as replication is an important feature that many depend on - it has to work.
In the last MySQL versions, we’ve seen improvements in replication performance through support for applying transactions in parallel. In MySQL 5.6, parallelization was done on schema level - all transactions which have been executed in separate schemas could be executed at once. This was a nice improvement for those workloads that had multiple schemas on a single server, and the load was distributed more or less evenly across the schemas.
In MySQL 5.7, another parallelization method was added, so called “logical clock”. It allowed to get some level of concurrency on a slave, even if all your data has been stored in a single schema. It was based, in short, on …
[Read more]In this posting we will look at currently recommended ways of managing passwords in MySQL Docker containers and explore whether the recently introduced concept of Docker Secrets could play a role in this area. Managing runtime secrets in Docker has traditionally been hard to do securely. The MySQL Docker images have typically offered various ways […]
In this post, we are going to explore the way of how to import a .csv file through the command line in dbForge Studio for MySQL. You will not have to waste your valuable time on manually specifying properties each time you need to create a new MySQL table. With this option, you can forget […]
In one of my previous posts, I shared InnoDB table compression statistics for a read-only dataset using the default value of innodb_compression_level (6). In it, I claimed, without giving much detail, that using the maximum value for the compression level (9) would not make a big difference. In this post, I will share more details about this claim.
TL;DR: tuning innodb_compression_level is not
In this post I’ll answer questions I received in my Wednesday, July 19, 2017, webinar Learning MySQL 5.7!
First, thank you all who attended the webinar. The link to the slides and the webinar recording can be found here.
I received a number of interesting questions in the webinar that I’ve followed up with below.
Would there be a big difference on passing from 5.1 to 5.6 before going to 5.7 or, at this point, would it be roughly the same?
The biggest risk of jumping between versions, in this case 5.1 to 5.6, is reverting in case of problems. Rollbacks don’t happen often, but they do happen and you have to make …
[Read more]
