Recently I had the discussion with one of my colleague about the impact of MySQL binary logs . It was a nice discussion and triggered me further to benchmark the MySQL with/without binary logs . The result is amazing

Server configuration :

• 4 CPU
• 8 GB RAM
• 100 GB SSD

MySQL version : 8.0.19

I have conducted the test with a bulk transaction . It is a single thread INSERT with 9.5 GB of data .

Test 1 – With binary log :

screen 1 :

from the screen 1, I had split my terminal to three screens .

1st screen : I have triggered the bulk INSERT

2nd screen : The INSERT has started to execute and in executing state .

3rd screen : You can see the individual table-space file ( .ibd ) keep growing ( 5.6 GB ) on …

I have been considering this for a while, but the 2019 edition of the MySQL Community Awards will be the final year. Over the past couple of years, the Percona Live conference has been expanding well beyond the walls of MySQL. There doesn’t seem to be an obvious event to hold the awards at, where there is both a large number of MySQL community members attending and the winners of the awards are also present.

The beauty of these awards was that there was no corporate entity involved – they were completely from the people and for the people. I was always really happy to give out an award to people that may not always be recognized and to celebrate what they had done.

The awards have been given out for 15 years now and they were picked up by the community from MySQL AB after 2009. I only managed the awards for a few years of the 15 total years, and before me — it was Shlomi Noach, and before him — Henrik Ingo. For a bunch of …

Codership is pleased to announce a new Generally Available (GA) release of Galera Cluster for MySQL 5.6 and 5.7, consisting of MySQL-wsrep 5.6.47 (release notes, download) and MySQL-wsrep 5.7.29 (release notes, download) with a new Galera Replication library 3.29 (release notes, download), implementing wsrep API version 25. This …

As hinted at earlier this month, we’re happy to announce our latest on-demand webinar:
“An Introduction to Database Proxies (for MySQL)”

In this webinar, Gilles Rayrat, our VP of Engineering and database proxies guru, shares some of his knowledge on the world of database proxies, how they work, why they’re important and what to use them for.

Starting with a simple database connectivity scenario, Gilles builds up the content by discussing clustered databases and what happens in the case of a failure through to explaining the important role database proxies play; including a more in-depth look into some advanced database connectivity setups and proxies functionalities.
…

Introduction In this article, we are going to see how the SQL EXISTS operator works and when you should use it. Although the EXISTS operator has been available since SQL:86, the very first edition of the SQL Standard, I found that there are still many application developers who don’t realize how powerful SQL subquery expressions really are when it comes to filtering a given table based on a condition evaluated on a different table. Database table model Let’s assume we have the following two tables in our database, that form a one-to-many... Read More

The post SQL EXISTS and NOT EXISTS appeared first on Vlad Mihalcea.

In my previous post (Puzzled by MySQL Replication), I describe a weird, but completely documented, behavior of replication that had me scratching my head for hours because it was causing data corruption.  I did not give too many details then as I also wanted allowing you to scratch your head if you wished.  In this post, I describe this behavior in more details.

But first I need to

We will have a look at a new feature in MySQL 8.0 called binlog encryption. This feature is available from the MySQL version 8.0.14 or above.

Our previous blogs discussed about table space encryption in MySQL and Percona servers. In Mydbops, we are giving high importance about achieving security compliances.

The binary log records changes made to the databases so that it can be used to replicate the same to the slaves and also for the point in time recovery (PITR). So, it means that if someone has access to the binary logs, they can reproduce our entire database in many forms. As a DBA, we need to make sure that the binary log files are protected from users who are having access to the file system and also, log files need …

We know the MySQL Shell is the advanced client tool for communicate to the MySQL server . MySQL Shell has lot of features like InnoDB Cluster control , InnoDB ReplicaSet, MySQL Shell utilities , MySQL server management etc … Today I came to know, MySQL shell helps lot in monitoring as well ( query, threads, resource consumption , locking ) .

In this blog I am going to explain how to use the MySQL Shell for monitor your server .

MySQL Shell provides two hot commands \show and \watch for monitor the MySQL server and report generating purpose .

\show : Execute the report with the provided options

\watch : Execute the report in loop with provided options

\show with thread example :

\show with query example :

You can execute any query within the double quotes .

\show with threads example :

From the initial release, one of the biggest complaints I had about Group Replication is that it allowed “stale” reads and there was no way to prevent them or to even know that you read “stale” data. That was a huge limitation. Thankfully, Oracle released features to control the consistency levels, and it was exactly a year ago! I don’t know about you, but I personally was confused by naming it group_replication_consistency=’AFTER’ or ‘BEFORE’.

So now I want to try to make sense of it and share my understanding (even if it is one year later).

Setup:

• 3 Node Percona Server for MySQL 8.0.18 running in …

As the second part of the earlier post Give Love to Your SSDs – Reduce innodb_io_capacity_max! we wanted to put together some concepts on how InnoDB flushing works in recent Percona Server for MySQL versions (8.0.x prior to 8.0.19, or 5.7.x). It is important to understand this aspect of InnoDB in order to tune it correctly. This post is a bit long and complex as it goes very deep into some InnoDB internals.

InnoDB internally handles flush operations in the background to remove dirty pages from the buffer pool. A dirty page is a page that is modified in memory but not yet flushed to disk. This is done to lower the write load and the latency of the transactions. Let’s explore the various sources of flushing inside InnoDB.

Idle Flushing

We already discussed the idle flushing in the previous post …