MySQL Community Advent Calendar 2022: How to deploy WordPress on OCI with MySQL Database Service and spread the read load to multiple Read Replicas

Oracle recently released Read Replica for MySQL Database Service (also known as MySQL HeatWave, with or without the use of HeatWave accelerator for OLTP and OLAP).

Read Replicas are read-only copies of the MySQL DB system in the same region. When you add Read Replicas, they are automatically distributed accross Availability Domains and/or Fault Domains.

Each MySQL DB instance can have up to 18 read replicas.

Read Replicas use MySQL Asynchronous Replication with parallel workers. And when you create the first Read Replica, a Read Replica Load Balancer is created, which distributes read traffic among the read replicas.

Not all shapes are compatible with Read Replicas, the …

I’ve said it before and I’ll say it again; I can only hope you enjoy reading the OpenLampTech developer newsletter as much as I do. Once again this week we have a fantastic newsletter for you (and me). Enjoy and please share the publication to help spread the word that OpenLampTech is the media coverage for MySQL, PHP, and the LAMP stack landscapes!

The Newsletter for PHP and MySQL Developers

Receive a copy of my ebook, “10 MySQL Tips For Everyone”, absolutely free when you subscribe to the OpenLampTech newsletter.

In OpenLampTech issue #56, we have curated and original content covering:

• A fantastic developer Interview
• 7 …

MySQL Community Advent Calendar 2022 - How to generate MySQL slow query log in OCI for MySQL HeatWave Database Service using Fn infrastructure - part 2

MySQL HeatWave Best Practices Series: Schema Design

MySQL Community Advent Calendar 2022 - How to generate MySQL slow query log in OCI for MySQL HeatWave Database Service using Fn infrastructure

MySQL Community Advent Calendar 2022 - How can you analyze queries in MySQL Database Service in OCI using Performance_Schema

In this blog, I’m going to discuss how to easily skip the replication errors in GTID (Global Transaction Identifier)-based replication.

In the MySQL world, if replication is broken we all use the famous SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; to skip the replication error. It always works if it’s a traditional binlogs events-based replication and is helpful to quickly resume the replication. But does this same method work for GTID-based replication? Let’s see.

In GTID-based replication, skipping a replication error in a broken replica is not as simple as binlogs-based replication. We have one old blog post — Repair MySQL 5.6 GTID replication by injecting empty transactions —where one of our colleagues showed us one way to skip and fix the replication.

Let’s get into action and …

Percona Server for MySQL 8.0.30-22 introduces a new authentication plugin, named authentication_fido. With this new plugin, it is possible to perform multi-factor authentication using hardware keys, or single-factor passwordless authentication with the same keys. This new plugin is in technical preview.

The plugin works exactly the same as the MySQL Enterprise FIDO authentication plugin, which is documented in detail in the official MySQL documentation and in the Percona Server for MySQL documentation

To try …

You now have more flexibility to configure Channels in MySQL Database Service for hybrid deployments or straightforward live migrations from on-premises or other cloud vendors. There are new options to add filters and source GTID handling in Channels for inbound replication.