Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Advanced MySQL 8

You're reading from   Advanced MySQL 8 Discover the full potential of MySQL and ensure high performance of your database

Arrow left icon
Product type Paperback
Published in Jan 2019
Publisher
ISBN-13 9781788834445
Length 286 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Birju Shah Birju Shah
Author Profile Icon Birju Shah
Birju Shah
Eric Vanier Eric Vanier
Author Profile Icon Eric Vanier
Eric Vanier
Tejaswi Malepati Tejaswi Malepati
Author Profile Icon Tejaswi Malepati
Tejaswi Malepati
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Introduction FREE CHAPTER 2. MySQL 8's New Features 3. Indexing Your Data for High Performance 4. Advanced Data Techniques for Large Queries 5. MySQL Data Dictionary in MySQL 8.0 6. MySQL Server Settings 7. Group Replication in MySQL 8.0 8. InnoDB Cluster in MySQL 8.0 9. Monitoring Your Large Distributed Databases 10. Authentication and Security Management with MySQL 8.0 11. Advanced MySQL Performance Tips and Techniques 12. Other Books You May Enjoy

Limitations of group replication

The following is a list of limitations for group replication:

  • Group replication works on top of a GTID-based replication, and it depends on transactions. So, we need tables with the InnoDB storage engine, which has transaction support.
  • CREATE TABLE...SELECT statements are not allowed, because the binlog_format maybe different on the master and slave. If the format is set to STATEMENT, the binary log will have one transaction with one GTID. If the format is set to ROW, the CREATE_TABLE..SELECT statement would result as two transactions with two GTIDs.
  • When the binary log format is set to STATEMENT, the creation of temporary tables and dropping temporary tables cannot be used inside transactions, functions, or triggers when we use GTID-based replication with auto commit set to 1. From MySQL 8.0.13, if the binary log format is set to ROW or MIXED...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime