summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorunknown <paul@teton.kitebird.com>2002-08-18 22:38:00 -0500
committerunknown <paul@teton.kitebird.com>2002-08-18 22:38:00 -0500
commitb138650ea0f115b0ed8ff46edef736bffe63bd63 (patch)
tree44d40d9fd3a50d82890eaee2ce95b922cf1bfb60
parente4f107b5acf0fd0ebcb1ab4041c8026ac4732e60 (diff)
downloadmariadb-git-b138650ea0f115b0ed8ff46edef736bffe63bd63.tar.gz
manual.texi fix option name typo
manual.texi fix typo Docs/manual.texi: fix option name typo
-rw-r--r--Docs/manual.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi
index dc1aa4a9ee0..a9fee2629dd 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -17800,7 +17800,7 @@ The different check types stand for the following:
@item @code{QUICK} @tab Don't scan the rows to check for wrong links.
@item @code{FAST} @tab Only check tables which haven't been closed properly.
@item @code{CHANGED} @tab Only check tables which have been changed since last check or haven't been closed properly.
-@item @code{MEDIUM} @tab Scan rows to verify that deleted links are okay. This also calculates a key checksum for the rows and verifies this with a calcualted checksum for the keys.
+@item @code{MEDIUM} @tab Scan rows to verify that deleted links are okay. This also calculates a key checksum for the rows and verifies this with a calculated checksum for the keys.
@item @code{EXTENDED} @tab Do a full key lookup for all keys for each row. This ensures that the table is 100% consistent, but will take a long time!
@end multitable
@@ -40550,7 +40550,7 @@ You may also want to change @code{binlog_cache_size} and
@item
To be able to rollback transactions BDB maintain log files. For maximum
performance you should place these on another disk than your databases
-by using the @code{--bdb_log_dir} options.
+by using the @code{--bdb-logdir} option.
@item
MySQL performs a checkpoint each time a new BDB log
file is started, and removes any log files that are not needed for