Remove GPDB_83_MERGE_FIXME for MirrorLock
GPDB still need MIRRORED_LOCK to be held to protect resync process
including:
- fileRepResyncShmem->appendOnlyCommitCount
- FileRepResyncManager_InResyncTransition()
Once the **File Replication** removed, we can remove the MIRRORED_LOCK.
The MirrorLock held exlusively at these places:
- `FileRepResyncManager_InResyncTransition()`
- `FileRepPrimary_RunResyncManager()`: where it used the lock to access
the counter `fileRepResyncShmem->appendOnlyCommitCount`.
Signed-off-by: NXin Zhang <xzhang@pivotal.io>
Showing
想要评论请 注册 或 登录