The MariaDB Foundation is pleased to announce the availability of MariaDB 10.3.13, the latest stable release in the MariaDB 10.3 series, as well as MariaDB Connector/C 3.0.9, the latest stable release in the MariaDB Connector/ODBC series. See the release notes and changelogs for details. Download MariaDB 10.3.13 Release Notes Changelog What is MariaDB 10.3? MariaDB […]
The post MariaDB 10.3.13 and MariaDB Connector/C 3.0.9 now available appeared first on MariaDB.org.
MySQL 8.0.15 performs worse in sysbench oltp_read_write than MySQL 5.7.25
Initially I was testing group replication performance and was puzzled why MySQL 8.0.15 performs consistently worse than MySQL 5.7.25.
It appears that a single server instance is affected by a performance degradation.
My testing setup
Hardware details:
Bare metal server
provided by packet.net, instance size: c2.medium.x86
24 Physical Cores @ 2.2 GHz
(1 X AMD EPYC 7401P)
Memory: 64 GB of ECC RAM
Storage : INTEL® SSD DC S4500, 480GB
This is a server grade SATA SSD.
Benchmark
sysbench oltp_read_write --report-interval=1 --time=1800 --threads=24 --tables=10 --table-size=10000000 --mysql-user=root --mysql-socket=/tmp/mysql.sock run
In the following summary I used these combinations:
In 8.0, we introduced window functions in the MySQL server. A detailed explanation of how window functions can be used and what is supported in 8.0 is explained here.
Now, let’s see what is new in window functions in the latest version 8.0.…
Facebook Twitter Google+ LinkedIn
Yesterday my Percona colleague Ceri Williams found a nasty bug
in MySQL 8.0.
Its twin for Percona Server reported at PS-5431.
He was installing MySQL Server 8.0 having not supported option in
his configuration file. Thus initialization failed, but,
surprisingly, the subsequent restart was successful and he was
able to create, modify and delete tables in his MySQL
installation. In other words: he got full access to the database.
But he did not create any user account yet!
This new instance of MySQL Server did not have privilege tables,
particularly …
In this tutorial, we will show you how to install and improve the security of MySQL on Ubuntu 18.04. MySQL ...
The post How to Install MySQL on Ubuntu 18.04 appeared first on RoseHosting.
Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL®, MongoDB®, and PostgreSQL performance. You can run PMM in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL®, MongoDB®, and PostgreSQL® servers to ensure that your data works as efficiently as possible.
In this release, we are introducing support for detection of our upcoming PMM 2.0 release in order to avoid potential version conflicts in the future, as PMM 1.x will not be compatible with PMM 2.x.
Another improvement in this release is we have updated the Tooltips for Dashboard MySQL Query Response Time by providing a description of what the graphs display, along with links to related documentation resources. An example of Tooltips in action:
…[Read more]ProxySQL in its versions up to 1.x did not natively support Percona XtraDB Cluster (PXC). Instead, it relied on the flexibility offered by the scheduler. This approach allowed users to implement their own preferred way to manage the ProxySQL behaviour in relation to the Galera events.
From version 2.0 we can use native ProxySQL support for PXC.. The mechanism to activate native support is very similar to the one already in place for group replication.
In brief it is based on the table
[runtime_]mysql_galera_hostgroups and the
information needed is mostly the same:
ProxySQL in its versions up to 1.x did not natively support
Percona XtraDB Cluster (PXC). Instead, it
relied on the flexibility offered by the scheduler. This approach
allowed users to implement their own preferred way to manage the
ProxySQL behaviour in relation to the Galera events. From version
2.0 we can use native ProxySQL support for PXC.. The mechanism to
activate native support is very similar to the one already in
place for group replication. In brief it is based on the table
[runtime_]mysql_galera_hostgroups and the
information needed is mostly the same:
MySQL Enterprise Backup (MEB) is a bit limited related to support of older MySQL versions. So you should consider the following release matrix:
| MEB/MySQL | Supported | 5.5 | 5.6 | 5.7 | 8.0 |
|---|---|---|---|---|---|
| 3.11.x | NO | x | x | ||
| 3.12.x | YES | x | x | ||
| 4.0.x | NO | x | |||
| 4.1.x | YES | x | …
I just encountered the problem described in the title, on a server I don’t have enough free space for create a backup as long the replica is catching up, because the relay logs eats all the available free space as the IO thread works faster than the SQL thread in the replication. What to do? […]
