MySQLReplication Feasibility Analysis _ MySQL

MySQLReplication feasibility analysis bitsCN.com

MySQL Replication Feasibility Analysis

AUTO_INCREMENT Version <5.5.30, AUTO_INCREMENT column-> AUTO_INCREMENT column ALL Yes www.bitsCN.com

Update AUTO_INCREMENT column by invoking a trigger or function! InnoDB No

The AUTO_INCREMENT column in the composite primary key is not the first column, and the INSERT operation is insecure. ALL No

Character Set Use UTF8 in master and slave InnoDB Yes

In the Temporary table mixed mode, update and insert operations are normal, but the on-demand counting of Temporary tables cannot be eliminated according to official instructions. InnoDB Yes can only be eliminated through stop slave; flush slave

Create if .. exists Mixed Mode normal InnoDB Yes

Create table .. select Mixed Mode normal InnoDB Yes

Create/Alter/Drop server requires independent InnoDB No maintenance from the database

Current_user () can be synchronized, and InnoDB Yes is usually not used

Drop .. If exists Mixed Mode normal InnoDB Yes

Memory table Mixed Mode: insert, read, and update. master/slave Memory tables must have the same size limit as InnoDB Yes www.bitsCN.com.

Rand (), UUID (), Last_insert_id () Only Mixed Mode InnoDB Yes

Limit Mixed Mode InnoDB Yes

Different table definition table definitions and engines can be Different, but the column order needs to be the same InnoDB Yes

Directory permission must assign InnoDB Yes to the path on the slave database

Invorked Features 5.5 may be updated across databases. Currently, InnoDB Yes can be synchronized normally.

Floating Point Value using Decimal can solve ALL No

Flush test scope: Flush Hosts/Slave/Logs; this type of maintenance Slave database requires independent InnoDB No www.bitsCN.com

System Function Mixed Mode-Row Base normal ALL Yes

Load Data infile 5.5.0 can be copied normally. after 5.5.6, use Mixed-Row Base ALL Yes.

Slow query log does not copy ALL No

The replication is stopped before the Repair table is maintained. after the maintenance is complete, the master-slave structure is manually ensured, and ALL No

Master and slave shutdown security operations, but when the master stops abnormally, data will be lost. You can set syn_binlog = 1 to reduce the loss. ALL No

Max_allowed_packet: when the maximum column (TEXT) is too large, causing the master to fail, the replication will terminate. ALL Yes

System database MySQL DB is synchronized normally, while the Mixed mode uses the RowBase mode. Conversely, the direct Update mode is ALL Yes.

Query optimizer depends on the syntax and may be inconsistent. ALL Yes

Reserved word mainly occurs when the new version adds Reserved words. after the new version appears, you need to modify the field name ALL Yes.

Set password and row-base rep are known bugs and are not copied. Master (5.1)-> slave (5.5); ALL No

Slave errors selects whether to skip the error based on the actual situation. For handling methods, refer to copy fault handling. Null

SQL mode master-slave unified SQL MODE can avoid ALL No

Retried and timeouts number of retries when the transaction is locked or times out. The default value of Document description is 10, and the actual default value is 0; ALL Yes

The Timestamp version is incorrect. if this problem is not found in 5.5, ALL Yes.

Time zones system-level Time synchronization ALL Yes

InnoDB Yes can be copied normally in Transactions Mixed mode.

Triggers does not use this feature. ALL Yes/No

Views copies to prevent tables that are specified to ignore replication. ALL Yes

InnoDB Yes can be copied normally in Truncate table Mixed mode.

Variables is maintained separately. Use my. cnf to manage related parameters in a unified manner. ALL No

Conclusion

According to the features required for database development and subsequent maintenance, the current replication can be used normally.

BitsCN.com