summaryrefslogtreecommitdiff
path: root/src/third_party/wiredtiger/src/docs/arch-log-file.dox
diff options
context:
space:
mode:
Diffstat (limited to 'src/third_party/wiredtiger/src/docs/arch-log-file.dox')
-rw-r--r--src/third_party/wiredtiger/src/docs/arch-log-file.dox2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/third_party/wiredtiger/src/docs/arch-log-file.dox b/src/third_party/wiredtiger/src/docs/arch-log-file.dox
index a4d544d595f..b8659a41c34 100644
--- a/src/third_party/wiredtiger/src/docs/arch-log-file.dox
+++ b/src/third_party/wiredtiger/src/docs/arch-log-file.dox
@@ -49,7 +49,7 @@ A hole can be generated in a log file if a buffer with a later LSN is written be
a buffer with an earlier LSN. That can also happen at a log file boundary and that is why
knowing the LSN at the end of the previous log file is critical to recovery.
-The user can choose the maximum log file size via \c log=(file_max=size) configuration
+The user can choose the maximum log file size via \c "log=(file_max=size)" configuration
to the ::wiredtiger_open call. Records written in the log are varying length
depending on the data written. In typical usage, the system will choose to switch
log files before writing a log buffer that exceeds the configured file size. However it