sql replication 성공
2020.02.20 21:51
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
1744 | Sinhala - සිංහල | WHRIA | 2024.05.24 | 12 |
1743 | Sundanese - Basa Sunda | WHRIA | 2024.05.24 | 13 |
1742 | Yiddish - ייִדיש | WHRIA | 2024.05.24 | 13 |
1741 | Chinese (Taiwan) - Chinese (Taiwan) | WHRIA | 2024.05.24 | 14 |
1740 | Danish - dansk | WHRIA | 2024.05.24 | 14 |
1739 | Romanian - română | WHRIA | 2024.05.24 | 14 |
1738 | Serbian - српски | WHRIA | 2024.05.24 | 14 |
1737 | Chinese (China) - 中文(中国) | WHRIA | 2024.05.24 | 15 |
1736 | Slovak - slovenčina | WHRIA | 2024.05.24 | 15 |
1735 | Slovenian - slovenščina | WHRIA | 2024.05.24 | 15 |
1734 | Tamil - தமிழ் | WHRIA | 2024.05.24 | 15 |
1733 | Thai - ไทย | WHRIA | 2024.05.24 | 15 |
1732 | Ukrainian - українська | WHRIA | 2024.05.24 | 15 |
1731 | Welsh - Cymraeg | WHRIA | 2024.05.24 | 15 |
1730 | Yoruba - Èdè Yorùbá | 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"