summaryrefslogtreecommitdiff
path: root/src/third_party
diff options
context:
space:
mode:
authorWill Korteland <will.korteland@mongodb.com>2022-03-10 04:33:36 +0000
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2022-03-10 05:00:08 +0000
commit7058241d1b32c535ec9f9270e462f3a922121013 (patch)
treeb867c71ee9233e256c1eeadc4a7864aa0b02d545 /src/third_party
parent0c818a98dc5634a1536818d44f23573f19e3ffbf (diff)
downloadmongo-7058241d1b32c535ec9f9270e462f3a922121013.tar.gz
Import wiredtiger: 5e2e0e9d66e7c02b5643257871280e63be420ab5 from branch mongodb-master
ref: 936758c1cf..5e2e0e9d66 for: 6.0.0 WT-6667 Document checkpoint's oldest timestamp behavior
Diffstat (limited to 'src/third_party')
-rw-r--r--src/third_party/wiredtiger/import.data2
-rw-r--r--src/third_party/wiredtiger/src/docs/timestamp-global.dox12
2 files changed, 10 insertions, 4 deletions
diff --git a/src/third_party/wiredtiger/import.data b/src/third_party/wiredtiger/import.data
index 015bb850279..4d057dd5fbb 100644
--- a/src/third_party/wiredtiger/import.data
+++ b/src/third_party/wiredtiger/import.data
@@ -2,5 +2,5 @@
"vendor": "wiredtiger",
"github": "wiredtiger/wiredtiger.git",
"branch": "mongodb-master",
- "commit": "936758c1cf25fdcb8adc24ad8a4ff73dfe4bbab0"
+ "commit": "5e2e0e9d66e7c02b5643257871280e63be420ab5"
}
diff --git a/src/third_party/wiredtiger/src/docs/timestamp-global.dox b/src/third_party/wiredtiger/src/docs/timestamp-global.dox
index 220b4fb6a78..3a895494156 100644
--- a/src/third_party/wiredtiger/src/docs/timestamp-global.dox
+++ b/src/third_party/wiredtiger/src/docs/timestamp-global.dox
@@ -40,9 +40,9 @@ WT_CONNECTION::set_timestamp method, including constraints.
| Timestamp | Constraints | Description |
|-----------|-------------|-------------|
-| durable_timestamp | <= oldest | Reset the maximum durable timestamp. |
-| oldest_timestamp | <= stable; may not move backward | Inform the system future reads and writes will never be earlier than the specified timestamp. |
-| stable_timestamp | may not move backward | Inform the system checkpoints should not include commits newer than the specified timestamp. |
+| durable_timestamp | <= oldest | Reset the maximum durable timestamp |
+| oldest_timestamp | <= stable; may not move backward, set to the value as of the last checkpoint during recovery | Inform the system future reads and writes will never be earlier than the specified timestamp. |
+| stable_timestamp | may not move backward, set to the recovery timestamp during recovery | Inform the system checkpoints should not include commits newer than the specified timestamp. |
@subsection timestamp_global_set_api_durable_timestamp Setting the global "durable_timestamp" timestamp
@@ -70,6 +70,9 @@ application update the oldest timestamp
frequently as retaining history can be expensive in terms of both cache and
I/O resources.
+During recovery, the \c oldest_timestamp is set to its value as of the checkpoint
+to which recovery is done.
+
Attempting to set the \c oldest_timestamp to a value earlier than its current
value will be silently ignored.
@@ -83,6 +86,9 @@ future checkpoint. Because tables in a timestamp world are generally using
checkpoint durability, the \c stable_timestamp also determines to point to which
recovery will be done after failures.
+During recovery, the \c stable_timestamp is set to the value to which recovery is
+performed.
+
The use of the \c stable_timestamp for checkpoints can be overridden in the call
to WT_SESSION::checkpoint.