sql replication 성공
2020.02.20 21:51
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
1744 | Georgian - ქართული | WHRIA | 2024.05.24 | 9 |
1743 | Galician - galego | WHRIA | 2024.05.24 | 1 |
1742 | French - français | WHRIA | 2024.05.24 | 10 |
1741 | Finnish - suomi | WHRIA | 2024.05.24 | 6 |
1740 | Filipino - Filipino | WHRIA | 2024.05.24 | 27 |
1739 | Estonian - eesti | WHRIA | 2024.05.24 | 6 |
1738 | Esperanto - esperanto | WHRIA | 2024.05.24 | 7 |
1737 | Danish - dansk | WHRIA | 2024.05.24 | 12 |
1736 | Dutch - Nederlands | WHRIA | 2024.05.24 | 24 |
1735 | Danish - dansk | WHRIA | 2024.05.24 | 14 |
1734 | Czech - čeština | WHRIA | 2024.05.24 | 17 |
1733 | Croatian - hrvatski | WHRIA | 2024.05.24 | 9 |
1732 | Corsican - Corsican | WHRIA | 2024.05.24 | 19 |
1731 | Chinese (Taiwan) - Chinese (Taiwan) | WHRIA | 2024.05.24 | 14 |
1730 | Chinese (China) - 中文(中国) | WHRIA | 2024.05.24 | 15 |
mysqldump --skip-lock-tables --single-transaction --flush-logs --hex-blob --master-data=2 -A > ~/dump.sql
Now, examine the head of the file and jot down the values for MASTER_LOG_FILE and MASTER_LOG_POS. You will need them later:
head dump.sql -n80 | grep "MASTER_LOG_POS"