Skip to content

Commit 41197f9

Browse files
committed
Updated after the review
1 parent 56b9446 commit 41197f9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/usage/oplog-replay.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,10 @@ PBM uses MongoDB's timestamp format for oplog replay, which provides operation-l
2020
You can define the oplog replay stop point in two ways:
2121

2222
1. **By ISO timestamp**:
23-
Specify an end time as an ISO timestamp (for example, `2025-01-02T15:00:00`). PBM converts this to `(epoch, 0)` and includes that operation. Use this method for convenience when the first operation within a specific second is sufficient.
23+
Specify an end time as an ISO timestamp (for example, `2025-01-02T15:00:00`). PBM converts this to `(epoch, 0)` and includes all oplog operations within that second. Use this method when you want to include all operations that occurred until the specified second.
2424

2525
2. **By MongoDB timestamp tuple**:
26-
Specify the stop point as `epoch,ordinal` (e.g., `1764576382,20`). PBM includes all operations up to that exact operation. Use this method when you need precise control over which specific operations within a second to include. This is especially useful when multiple operations occurred at the same time.
26+
Specify the stop point as `epoch,ordinal` (e.g., `1764576382,20`). PBM includes all operations up to that exact operation. Use this method when you need precise control over which specific operations within a second to include.
2727

2828
## Oplog replay for physical backups
2929

0 commit comments

Comments
 (0)