Author - Marcelo Altmann

MySQL Single Table Point-In-Time Recovery

Point-In-Time Recovery

In this blog post, I’ll look at how to execute a MySQL single table Point-In-Time Recovery.
I recently wrote a blog post describing a different way of doing Point-In-Time Recovery (PITR). If you want to know the step by step, please visit the mentioned blog post. Here is a quick summary of the approach:

Restore the backup […]

Read more

MySQL Point in Time Recovery the Right Way

MySQL Point In Time Recovery

In this blog, I’ll look at how to do MySQL point in time recovery (PITR) correctly.
Sometimes we need to restore from a backup, and then replay the transactions that happened after the backup was taken. This is a common procedure in most disaster recovery plans, when for example you accidentally drop a table/database or run […]

Read more

MySQL super_read_only Bugs

MySQL error code 1215

This blog we describe an issue with MySQL 5.7’s super_read_only feature when used alongside with GTID in chained slave instances.
Background
In MySQL 5.7.5 and onward introduced the gtid_executed table in the MySQL database to store every GTID. This allows slave instances to use the GTID feature regardless whether the binlog option is set or not. Here is […]

Read more

When MySQL Lies: Wrong seconds_behind_master with slave_parallel_workers > 0

MySQL error code 1215

In today’s blog, I will show an issue with seconds_behind_master that one of our clients faced when running slave_parallel_workers > 0. We found out that the reported seconds_behind_master from SHOW SLAVE STATUS was lying. To be more specific, I’m talking about bugs #84415 and #1654091.
The Issue
MySQL will not report the correct slave lag if you have slave_parallel_workers > […]

Read more