3064
MySQLWARNINGNotableReplicationHIGH confidence
MASTER_LOG_FILE specified without MASTER_LOG_POS
Production Risk
Medium — can cause duplicate data or replication errors.
What this means
CHANGE MASTER TO specified MASTER_LOG_FILE without a corresponding MASTER_LOG_POS, which may lead to an unexpected replication start position.
Why it happens
- 1CHANGE MASTER TO MASTER_LOG_FILE='...' used without MASTER_LOG_POS.
How to reproduce
trigger — this will error
trigger — this will error
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000001';
expected output
Warning (Code 3064): CHANGE MASTER TO without MASTER_LOG_POS will use position 4 by default.
Fix
Always specify both MASTER_LOG_FILE and MASTER_LOG_POS
Always specify both MASTER_LOG_FILE and MASTER_LOG_POS
CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=4;
Why this works
Explicit position prevents unexpected replication start points.
What not to do
✕
Sources
Official documentation ↗
MySQL 8.0 — 3064 ER_WARN_ONLY_MASTER_LOG_FILE_NO_POS2
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev