For the third day of our Advent Calendar of Content, we bring you a summary of all the MySQL Shorts that are focussed on HeatWave MySQL

With the successful deployment of MySQL Enterprise Edition, Lina One has improved telemarketing productivity across its call centers and set a new standard for efficiency and security in the insurance industry. Read the blog.

Tagging is an essential practice in managing and organizing cloud resources. In Oracle Cloud Infrastructure (OCI), tagging is an integral part of the OCI Identity and Access Management service(IAM) which provides a systematic way to categorize and manage resources effectively, such as cost tracking, cloud resource searching, filtering and logical organization.

In this blog post, we will explore how to use cost tags to correlate the cost associated with a particular HeatWave MySQL DB System.

MySQL 8.4 and newer have extended the Global Transaction ID (GTID) functionality with a new “tag” option.

Refresher on GTID

A GTID is a unique ID that is assigned to a transaction. This is used if gtid_mode is set to ON. The benefit of this is that a transaction can be uniquely identified in a MySQL replication setup with multiple levels. Among others this makes it easier to refactor a replication tree as a MySQL replica knows which transactions it has seen and can use this to find the right position to start replicating from a new source.

The format of GTIDs is documented here.

Before GTID was used replication worked based on a file and offset (e.g. file=binlog.000001,offset=4), which is unique to every server.

A GTID without tag looks like …

I am writing this quick post to share what I think is a problematic new behavior of Offline Mode in MySQL 9.  Basically, the new default behavior in MySQL 9 is to write the username of the user which set offline_mode to ON.  I think this behavior has not been considered from a security point of view because it leaks a root username in the error message presented to the users.

My

The latest episode of MySQL Shorts is now available.

As part of the Advent calendar of content for this year, we are going to take a stroll down memory lane into the history of MySQL. In this first post, we will highlight some of the major milestones of the early years.

Learn about the merge replication topology used for building scalable, bi-directional, multi-primary replication deployments using MySQL NDB Cluster. This topology makes it possible to reliably scale out circular replication forming three, four, or more clusters all containing the same data.

MySQL 8.4 changes the default values of built-in configurations when compared to MySQL 8.0. These changes are designed to auto adapt with the machine making the MySQL server production ready out of the box.

In the last weeks / months, I have been working on understanding / improving MySQL startup with many tables.  I already wrote four posts on the subject, they are listed below.  In this post, I use the system analysis of the previous post to revisit the light optimization on EBS volumes.  With this analysis, I am able to determine why the previous tests did not show