Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
MariaDB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
MariaDB
Commits
6eac4406
Commit
6eac4406
authored
Aug 27, 2002
by
unknown
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
manual.texi minor fixes
Docs/manual.texi: minor fixes
parent
1e747dc7
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
4 deletions
+5
-4
Docs/manual.texi
Docs/manual.texi
+5
-4
No files found.
Docs/manual.texi
View file @
6eac4406
...
...
@@ -7830,7 +7830,7 @@ reload the grant tables.
@cindex problems, starting the server
If you are going to use tables that support transactions (InnoDB, BDB),
you should first create a
my.cnf
file and set startup options
you should first create a
@file{my.cnf}
file and set startup options
for the table types you plan to use. @xref{Table types}.
Generally, you start the @code{mysqld} server in one of these ways:
...
...
@@ -40421,7 +40421,7 @@ they roll back the corresponding SQL statement.
@strong{Warning}: do @strong{NOT} convert MySQL system tables from
MyISAM TO InnoDB tables! This is not supported; if you do this MySQL
will not restart until you restore the old system tables from a backup
or re-generate them with the
mysql_install_db
script.
or re-generate them with the
@code{mysql_install_db}
script.
@item
@code{SHOW TABLE STATUS} does not give accurate statistics
...
...
@@ -40593,7 +40593,7 @@ BDB tables:
@item @code{--bdb-no-sync} @tab Don't synchronously flush logs.
@item @code{--bdb-no-recover} @tab Don't start Berkeley DB in recover mode.
@item @code{--bdb-shared-data} @tab Start Berkeley DB in multi-process mode (Don't use @code{DB_PRIVATE} when initialising Berkeley DB)
@item @code{--bdb-tmpdir=directory} @tab Berkeley DB temp
file name
.
@item @code{--bdb-tmpdir=directory} @tab Berkeley DB temp
orary file directory
.
@item @code{--skip-bdb} @tab Disable usage of BDB tables.
@item @code{-O bdb_max_lock=1000} @tab Set the maximum number of locks possible. @xref{SHOW VARIABLES}.
@end multitable
...
...
@@ -40767,7 +40767,8 @@ Here follows the restrictions you have when using BDB tables:
@itemize @bullet
@item
BDB tables store in the .db file the path to the file as it was created
BDB tables store in the @file{.db} file the path to the file as it was
created.
This was done to be able to detect locks in a multi-user
environment that supports symlinks).
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment