[MDEV-17819] Replication documentation suggests current_pos instead of slave_pos Created: 2018-11-23  Updated: 2018-11-27  Resolved: 2018-11-27

Status: Closed
Project: MariaDB Server
Component/s: Documentation
Affects Version/s: N/A
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: markus makela Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: None


 Description   

The Setting Up Replication and Global Transaction ID documents both recommend the use of current_pos.

To my knowledge, slave_pos should be used in most cases as it always refers to the latest replicated event instead of the latest processed event, the latter of which also includes events generated on the slave server. If current_pos is used instead of slave_pos, any local transactions on a slave will prevent replication from starting correctly.


Generated at Thu Feb 08 08:39:21 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.