The MySQL Development team is very happy to announce that MySQL 8.0.19 is now available for download at dev.mysql.com. In addition to bug fixes there are a few new features added in this release. Please download 8.0.19 from dev.mysql.com or from the MySQL Yum, APT, or SUSE repositories.…
Facebook Twitter LinkedIn
MySQL will be in Dubai from JAN13-15.
JAN 13 – 7PM-10PM – MySQL Meetup at Place: Dubai Internet City
Learn more: https://www.meetup.com/MySQL-User-Group-U-A-E/events/267697018/
JAN 14-15 - Oracle Open World - Dubai
…
[Read more]Queries effect database performance. That’s not a typo: “effect” not “affect”. The difference is not a word game but an important way to think about database performance.
Many things can affect performance. For example, if the system runs out of memory then starts swapping which causes high disk IO latency, that will negatively affect performance. But external factors like that notwithstanding (i.e. when hardware and MySQL are normal and stable), it’s important to understand that queries effect performance.
Queries effect database performance. That’s not a typo: “effect” not “affect”. The difference is not a word game but an important way to think about database performance. Many things can affect performance. For example, if the system runs out of memory then starts swapping which causes high disk IO latency, that will negatively affect performance. But external factors like that notwithstanding (i.e. when hardware and MySQL are normal and stable), it’s important to understand that queries effect performance.
So far, I have written two tutorial blogs about MySQL InnoDB Cluster . Those blogs describe about the InnoDB Cluster configuration and how to integrate InnoDB Cluster with the MySQL router . You can get them through the below links .
In this blog I am going to explain the following two things ,
In the many years we have used MySQL, we got accustomed to the fact that upgrades from MySQL 5.7.11 to 5.7.12 was a minor event. This meant that if something was going wrong, we could roll back the binaries and be happy again.
From MySQL 8, this is no longer true. Any upgrade, even minor, is seen as irreversible. (This is valid for Percona Server for MySQL as well.)
Say we have MySQL 8.0.17 and we upgrade to 8.0.18. In our MySQL log at the start, we will have this:
[System] [MY-010116] [Server] /opt/mysql_templates/mysql-8P/bin/mysqld (mysqld 8.0.18) starting as process 13242 … [System] [MY-013381] [Server] Server upgrade from '80017' to '80018' started. … [System] [MY-013381] [Server] Server upgrade from '80017' to '80018' completed. … [System] [MY-010931] [Server] /opt/mysql_templates/mysql-8P/bin/mysqld: …[Read more]
I am writing a tutorial on the MySQL Document Store for the sold
out (sorry) pre-FOSDEM MySQL days. For those who do not
write such exercise they are often a difficult task as you have a
limited time to convey information, need to provide vivid
examples, and create exercises that give a good idea of what the
topic is all about. And my personal preference is to write
once and use the tutorial at other events (please let me know
if you have such an event).
Indexing records is a well know performance step when creating
databases, SQL or NoSQL. And back in June of 2017 I wrote a
blog post on using createIndex() to index documents in the
MySQL Document Store. And as part of creating the tutorial I
referred to that blog post as a reference and was quite surprised
that it was not working.
What happened? Well back in 8.0.11 the function was revised and
it is no longer a series of chained calls but …
If you are thinking of using ProxySQL in our Percona XtraDB Cluster environment, I’ll explain how to use ProxySQL 2 for failover tasks.
How to Test
ProxySQL uses the “weight” column to define who is the WRITER node. For this example, I’ll use the following list of hostnames and IPs for references:
+-----------+----------------+ | node_name | ip | +-----------+----------------+ | pxc1 | 192.168.88.134 | | pxc2 | 192.168.88.125 | | pxc3 | 192.168.88.132 | +-----------+----------------+
My current WRITER node is the “pxc1” node, but how can I see who is the current WRITER? It’s easy, just run the following query:
proxysql> select hostgroup_id, comment, hostname, status, weight from runtime_mysql_servers;
This is the output: …
[Read more]The management of database performance is an area that businesses when administrators often find themselves contributing more time to than they expected.
Monitoring and reacting to the production database performance issues is one of the most critical tasks within a database administrator job. It is an ongoing process that requires constant care. Application and underlying databases usually evolve with time; grow in size, number of users, workload, schema changes that come with code changes.
Long-running queries are seldom inevitable in a MySQL database. In some circumstances, a long-running query may be a harmful event. If you care about your database, optimizing query performance, and detecting long-running queries must be performed …
[Read more]The importance of having periodic backups is a given in Database life. There are different flavors: binary ones (Percona XtraBackup), binlog backups, disk snapshots (lvm, ebs, etc) and the classic ones: logical backups, the ones that you can take with tools like mysqldump, mydumper, or mysqlpump. Each of them with a specific purpose, MTTRs, retention policies, etc.
Another given is the fact that taking backups can be a very slow task as soon as your datadir grows: more data stored, more data to read and backup. But also, another fact is that not only does data grow but also the amount of MySQL instances available in your environment increases (usually). So, why not take advantage of more MySQL instances to take logical backups in an attempt to make this operation faster?
Distributed Backups (or Using all the Slaves Available)
…
[Read more]