In the use of MySQL, often in the table to establish a self-increment ID field, the use of self-increment ID can be quickly indexed, is also the official MySQL recommended way, but this way in a large number of data and configuration of master-slave, may occur due to the self-increment ID caused by synchronization failure First need to understand a little MySQL master-slave synchronization mainly through the bin log to synchronize, and MySQL bin log maximum value is 1G, this condition is as follows: 1, the database configuration master-Slave synchronization 2, the table exists self-ID3, table data volume is large,
If the Lord performs an insert Into...select ... Class SQL, when the SQL thing exceeds 1G, MySQL synchronizes the SQL from the row mode, which is synchronous to insert into values (...), when the amount of data exceeds 1G, which exceeds the maximum allowable value of MySQL bin log, so master-slave synchronization fails , you can only delete the self-increment field to restore Master and slave. Use the self-increment field sparingly on a table with a large amount of data and the above computed SQL
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.