This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
linux:databases:mysql [2017/11/21 22:45] tkilla |
linux:databases:mysql [2017/11/22 01:10] (current) tkilla |
||
---|---|---|---|
Line 87: | Line 87: | ||
- | interesting for replication: | + | Restart mysql and check to see current setting: |
+ | SHOW VARIABLES LIKE ' | ||
- | | ||
- | | ||
- | --single-transaction | ||
- | BUT | ||
- | will give you an exact point-in-time snapshot of the data | ||
- | | ||
- | | ||
- | Those incoming changes do not become part of the dump. That ensures the same point-in-time for all tables. | ||
- | USE IF ALL TABLES ARE INNODB | ||
- | --opt includes --lock-tables | + | |
+ | interesting parameters for replication: | ||
+ | |||
+ | --lock-tables - READ LOCK (no writes) for currently dumped database: ensures consitent dump instead of | ||
+ | --single-transaction | ||
+ | will give you an exact point-in-time snapshot of the data | ||
+ | --single-transaction produces a checkpoint that allows the dump to capture all data prior to the | ||
+ | checkpoint while receiving incoming changes. | ||
+ | Those incoming changes do not become part of the dump. That ensures the same point-in-time for all tables. | ||
+ | USE IF ALL TABLES ARE INNODB | ||
+ | |||
+ | --opt includes --lock-tables | ||
---- | ---- | ||