Care to give some detail about the usecase for a single transaction affecting 9 GB of data? Apart from backup restoration, that seems quite an anti-pattern…

LikeLiked by 1 person

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 …

• In-built columnar storage engine that works next to Innodb on the same DB server.
• Materialized views - async and semi-immediate
• Recommended indexes based on query usage
• Rename CREATE PROCEDURE to CREATE DATABASE API. Yes, really.. just rename it.

INTERVIEW: Bernd Ocklin at Pre FOSDEM MySQL Day 2020 in Brussels
Interview

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 …

A sold out, two-day event with over 30 sessions on various aspects of MySQL is a tough thing to organize and accomplish. But the MySQL pre-FOSDEM Days was an amazing success. If you missed this event then you really missed two full days of presentations by MySQL engineers and subject matter experts from the MySQL Community. 


It all started on Thursday January 30th with Geir Hoydalsvik talking about Simplifying MySQL which not a simple talk.  Big efforts are being made to clean up and modernize the MySQL Server Core code.  Work is being undertaken to change to a Volcano Model for extended flexibility. 

This was followed by Kenny Gryp showing how the new InnoDB Replica Set. Previously it was easier to setup InnoDB Cluster Replication than simple …

i was working on some example code for using check constraints and was fairly happy with my first bit of of code.

CREATE TABLE c1 (x INT 
                   CONSTRAINT x_gt_0 CHECK (x > 0)
);

it worked well and did what I wanted which was to reject data where the value for x was not one or greater. MySQL has allowed you to have constraint checks for many years but they only came to life in 8.0.16.  Before that version the checks were simply ignored.

So I was writing some more demo code and smacked into what I thought was an odd error.

CREATE TABLE c2 (x INT 
                   CONSTRAINT x_gt_0 CHECK (x > 0), 
                   CONSTRAINT …

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 …

This is the tutorial and serves as a sample ONLY.  Every environment can be different.  It is a test trial for the Upgrade MySQL InnoDB Cluster with version 5.7.25 to MySQL 8.0.19 where the MySQL InnoDB Cluster Metadata has changed from V1 to V2 in 8.0.19.
1.      Assuming the following SETUP            i.              MySQL Server 5.7.25           ii.              MySQL Shell : 8.0.15         iii.              MySQL Router : 8.0.15 2.      3 nodes are running on the same machine for this tutorial            …

Monitoring is a must in all environments, and databases aren’t the exception. Once you have your database infrastructure up-and-running, you’ll need to keep tabs on what’s happening. Monitoring is a must if you want to be sure everything is going fine but also if you make necessary adjustments while your system grows and evolves. That will enable you to identify trends, plan for upgrades or improvements, or react adequately to any problems or errors that may arise with new versions, different purposes, and so on.

For each database technology, there are different things to monitor. Some of these are specific to the database engine, vendor, or even the particular version that you’re using. Database clusters heavily depend on the underlying infrastructure, so network and operating stats are interesting to see by the database administrators too. 

When running multiple database systems, the monitoring of these systems can …