This post is for the backup script for MySQL database on Linux with mail. It’s a linux shell script for taking logical backup using mysqldump and sending status email. The backup shell script works as follows: – The script takes backup using mysqldump and compresses it. – Upon success, it will attempt to ship the […]
10 Older Entries »
You say you want a Replication?
One of the best features of MySQL is the ability to use MySQL‘s built-in database replication feature to automatically replicate data from one server (source/master) to another (slave/replica). Group Replication was added in MySQL 5.7 as a way to provide a high-availability solution using a new variation of MySQL replication.
(In some earlier posts, I explained how to setup Group Replication using three MySQL database servers and how to …[Read more]
More than 3 weeks passed since my previous review of public MySQL bug reports I
am subscribed to, so it's time to present some of the bugs I've
considered interesting in January, 2019.
As usual, I'll review them starting from the oldest and try to summarize my feelings about these bugs at the end of this post. Here they are:
- Bug #93806 - "Document error about ON DUPLICATE KEY UPDATE". Years pass, but fine MySQL manual still does not explain some cases of InnoDB locking properly. Xiaobin Lin found yet another case that it does not explain properly. Or, maybe, the manual is correct and the problem in …
Holidays season is almost over here, so it's time to get back to
my main topic of MySQL bugs. Proper MySQL bug reporting will be a
topic of my FOSDEM 2019 talk in less than 4 weeks (and few
slides with recent examples of bugs are not yet ready), so I have
to concentrate on bugs.
Last time in this series I reviewed some interesting bug reports filed in November, 2018. Time to move on and proceed with bugs reported in December, 2018, as I've subscribed to 27 or so of them. As usual, I'll review them briefly starting from the oldest and try to check if MariaDB 10.3 is also affected when the bug report is about common features:
From the lack of comments to my previous post it seems everything is clear with ERROR 1213 in different kinds and forks of MySQL. I may still write a post of two about MyRocks or TokuDB deadlocks one day, but let's get back to my main topic of MySQL bugs. Today I continue my series of posts about community bug reports I am subscribed to with a review of bugs reported in November, 2018, starting from the oldest and skipping those MySQL 8 regression ones I've already commented on. I also skip documentation bugs that should be a topic for a separate post one day (to give more illustration to …[Read more]
For some reason the Committee of FOSDEM 2019
MySQL, MariaDB & Friends Devroom of all my talks
submitted picked up the one on how to create a useful MySQL bug
report, so I have no options but continue to write about MySQL
bugs, as long and MySQL Community wants and even prefers to
listen and read about them... That's what I do, with
Today I'll continue my series of posts about community bug reports I am subscribed to with the review of bugs reported since October 1, 2018, starting from the oldest and skipping those MySQL 8 regression ones I've already commented on:
This tutorial is for you that is trying to import your current
database into a Google Cloud SQL instance,
that will be setup for replication purposes.
According to the documentation, you will need to run:
mysqldump \ -h [MASTER_IP] -P [MASTER_PORT] -u [USERNAME] -p \ --databases [DBS] \ --hex-blob --skip-triggers --master-data=1 \ --order-by-primary --compact --no-autocommit \ --default-character-set=utf8 --ignore-table [VIEW] \ --single-transaction --set-gtid-purged=on | gzip | \ gsutil cp - gs://[BUCKET]/[PATH_TO_DUMP]
mysqldump parameters are:
-hthe hostname or IPV4 address of the
-Pthe port or the
primaryserver, usually …
How to Restore A Table / Database From Full Backup using MySQL Grants & mysqldump.
While MySQL 8.0.x hardly has much impact on my regular work,
recent MySQL 5.7.20 release is something to check carefully.
MySQL 5.7 is widely used in production, as a base for Percona
Server 5.7, some features may be merged into MariaDB 10.x etc.
So, here is my review of some community reported bugs that were
fixed in recently released MySQL 5.7.20, based on the release notes.
Usually I start with InnoDB bug fixes, but in 5.7.20 several related fixes were made only to bugs reported internally. So, this time I have to start with partitioning:
- Bug #86255 - First one to write about, and the bug report is …
More than 3 months after 5.7.18 we' ve got MySQL 5.7.19 released
recently. This is my quick review of the release notes with interesting fixed bug
(reported in public) highlighted in the areas I am usually
Let's start with InnoDB. The following bug fixes attracted my attention:
- Bug #85043 is still private. You know how much I hate those. At least we can see it was about the fact that "The server allocated memory unnecessarily for an operation that rebuilt the table." Let's hope this is no longer the case.
- Bug …
10 Older Entries »