Please turn JavaScript on
J-F Gagné's MySQL Blog icon

J-F Gagné's MySQL Blog

Want to stay in touch with the latest updates from J-F Gagné's MySQL Blog? That's easy! Just subscribe clicking the Follow button below, choose topics or keywords for filtering if you want to, and we send the news to your inbox, to your phone via push notifications or we put them on your personal page here on follow.it.

Reading your RSS feed has never been easier!

Website title: J-F Gagné's MySQL Blog

Is this your feed? Claim it!

Publisher:  Unclaimed!
Message frequency:  0.07 / day

Message History

I have known for some times that there is an interesting improvement in MySQL 8.0.17 regarding GTID Crash Safety, but I have not had the time nor the need to look into it before.  When writing my last post (Understanding MySQL Replication "fatal error 1236": [...]), I saw something interesting related to this, and it is now time to cover this on my blog. From my point of view, t...

Read full story
This MySQL replication error — fatal error 1236 / Replica has more GTIDs than the source has, using the source's SERVER_UUID — shows the importance of thinking before acting. I am glad a non-DBA Colleague asked me about this error, because if he would just have restarted replication, it would have caused a much bigger mess. Often, we are tempted — or pushed — to just

Read full story
Today, I was reminded of a MySQL Best Practice, probably generalizable to all databases : using simple types, not complex types.  Such complex types to avoid include the date and time data types (including TIMESTAMP) and ENUM.  Let's see why. A little history about this, Baron Schwartz, a MySQL Legend who is not involved in the community anymore, compared using the TIMESTAMP ...

Read full story