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

How to use MySQL Shell to run JavaScript and Python scripts to connect to a MySQL database and execute queries. In this example, I show you how to dump and load a database table with a JavaScript script.

Within this blog post, we want to thanks all our contributors and list all the contributions that have been processed and released with MySQL 9.1

Last month we released MySQL 9.1, the latest Innovation Release. Of course, we released bug fixes for 8.0 and 8.4 LTS but in this post, I focus on the newest release. Within these releases, we included patches and code received by our amazing Community. Here is the list of contributions we processed and included in […]

This blog outlines how MySQL Enterprise Edition enhances developer agility and performance in financial services.

RBL Bank's strategic shift to MySQL Enterprise Edition fortified its cybersecurity defenses and streamlined operations, positioning the bank for continued growth and customer satisfaction in the competitive banking landscape. Read the blog.

Customer contacts in HeatWave is a new feature that streamlines notification management by allowing you to assign specific contacts for all critical databases. With this capability, your Cloud Ops and DBA team can stay informed about operational issues, maintenance updates, and service announcements, ensuring timely responses.

With multi-threaded replication (MTR), a replica can commit transactions in the same order as the source, or not. This is determined by sysvar replica_preserve_commit_order (RPCO). As of MySQL v8.0.27 (released October 2021) it’s ON by default, but it was OFF by default for several years prior. In either case, it’s relatively new compared to 20+ years of single-threaded replication for which commit order was not an issue or option. But with MTR, it’s important to understand the affects of RPCO, especially with respect to the focus of this three-part series: replication lag.

I recently became aware of WeSQL. A MySQL-compatible database that separates compute and storage, using S3 as the storage layer. The product uses a columnar format by default which is significantly more space-efficient than InnoDB.

WeSQL introduces a new storage engine called SmartEngine using a LSM-tree-based structure that is ideal for a storage bucket implementation, and documentation shows the implementation of raft replication to combat latency concerns. There is a lot more information to review, the serverless architecture and WeScale, a database proxy and resource manager.

It was very easy to take it for an initial spin using a docker container and an AWS S3 bucket. I would really like to try CloudFlare R2 which implements the S3 API.

Under the covers there …