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
00eba7a2
Commit
00eba7a2
authored
Nov 27, 2000
by
tim@threads.polyesthetic.msg
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
manual.texi more berkeley db documentation
parent
5a9c1a96
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
72 additions
and
46 deletions
+72
-46
Docs/manual.texi
Docs/manual.texi
+72
-46
No files found.
Docs/manual.texi
View file @
00eba7a2
...
@@ -5364,6 +5364,12 @@ into it.
...
@@ -5364,6 +5364,12 @@ into it.
Obtain a distribution file from one of the sites listed in
Obtain a distribution file from one of the sites listed in
@ref{Getting MySQL, , Getting @strong{MySQL}}.
@ref{Getting MySQL, , Getting @strong{MySQL}}.
@item
If you are interested in using Berkeley DB tables with MySQL, you
will need to obtain a patched version of the Berkeley DB source
code. Please read the chapter on Berkeley DB tables before
proceeding. @xref{BDB}.
@strong{MySQL} source distributions are provided as compressed @code{tar}
@strong{MySQL} source distributions are provided as compressed @code{tar}
archives and have names like @file{mysql-VERSION.tar.gz}, where
archives and have names like @file{mysql-VERSION.tar.gz}, where
@code{VERSION} is a number like @value{mysql_version}.
@code{VERSION} is a number like @value{mysql_version}.
...
@@ -5708,32 +5714,31 @@ source tree:
...
@@ -5708,32 +5714,31 @@ source tree:
@itemize
@itemize
@item
@item
Download @strong{BitKeeper} from @uref{http://www.bitmover.com/cgi-bin/download.cgi}
Download @strong{BitKeeper} from @uref{http://www.bitmover.com/cgi-bin/download.cgi}
.
@item
@item
Follow the instructions to install it
Follow the instructions to install it
.
@item
@item
Once @strong{BitKeeper} is installed,
Once @strong{BitKeeper} is installed,
@code{bk clone bk://work.mysql.com:7000 mysql} - the initial download
@code{bk clone bk://work.mysql.com:7000 mysql} - the initial download
may take a while, depending on the speed of your connection
may take a while, depending on the speed of your connection
.
@item
@item
@code{cd mysql; bk -r edit; aclocal; autoheader; autoconf;
@code{cd mysql; bk -r edit; aclocal; autoheader; autoconf;
automake; ./configure} with your favorite options, and then
automake; ./configure} with your favorite options, and then
@code{ make}
@code{ make}
.
- y
ou will need GNU autoconf/automake, libtool, and m4 to do this.
Y
ou will need GNU autoconf/automake, libtool, and m4 to do this.
.
We have a
We have a
collection of our standard configure scripts in the @code{BUILD/}
collection of our standard configure scripts in the @code{BUILD/}
subdirectory - if you are lazy, you can do
subdirectory - if you are lazy, you can do
@code{BUILD/compile-pentium-debug} . It will actually work on a lot of
@code{BUILD/compile-pentium-debug} . It will actually work on a lot of
non
e
-x86 machines despite its name.
non-x86 machines despite its name.
@item
@item
Once the build is done, @code{make install}. Be careful with this on
Once the build is done, @code{make install}. Be careful with this on
a production machine - this may overwrite your live release binary. We
a production machine - this may overwrite your live release binary. We
recommend that if you have another installation of @strong{MySQL} that
recommend that if you have another installation of @strong{MySQL} that
you @code{./configure} with different values for @code{basedir},
you @code{./configure} with different values for @code{prefix},
@code{datadir}, @code{bindir}, @code{sbindir}, @code{libexecdir},
@code{tcp-port}, and @code{unix-socket-path}.
@code{tcp-port}, and @code{unix-socket-path}
@item
@item
Play hard with your new installation and try to make the new feature
Play hard with your new installation and try to make the new feature
s
crash. Report bugs to @email{bugs@@lists.mysql.com}. As always, make
crash. Report bugs to @email{bugs@@lists.mysql.com}. As always, make
sure you have a full test case for the bug that we can run.
sure you have a full test case for the bug that we can run.
@item
@item
...
@@ -5745,18 +5750,18 @@ if you execute @code{aclocal} and get @code{command not found}, or a
...
@@ -5745,18 +5750,18 @@ if you execute @code{aclocal} and get @code{command not found}, or a
similar problem, do not report it - make sure all the needed tools are
similar problem, do not report it - make sure all the needed tools are
installed and your @code{PATH} variable is set correctly.
installed and your @code{PATH} variable is set correctly.
@item
@item
After the initial @code{bk clone}, do @code{bk pull} to get the updates
After the initial @code{bk clone}, do @code{bk pull} to get the updates
.
@item
@item
You can examine change history
to the tree with all the cool
diffs with
You can examine change history
of the tree with all the
diffs with
@code{bk sccstool}. If you see some funny diffs or code that you have a
@code{bk sccstool}. If you see some funny diffs or code that you have a
question about, do not hesitate and e-mail
question about, do not hesitate and e-mail
@email{internals@@lists.mysql.com}. Also if you think you have a
@email{internals@@lists.mysql.com}. Also if you think you have a
better idea on how to do something, send an email to the same place
better idea on how to do something, send an email to the same place
with a patch - @code{bk diffs} wi
th
produce a patch for you after you
with a patch - @code{bk diffs} wi
ll
produce a patch for you after you
have made changes to the source. If you do not have the time to code
have made changes to the source. If you do not have the time to code
your idea, just send a description.
your idea, just send a description.
@item
@item
@strong{BitKeeper} has a nice help utility - @code{bk helptool}
@strong{BitKeeper} has a nice help utility - @code{bk helptool}
.
@end itemize
@end itemize
...
@@ -5989,7 +5994,7 @@ Note that on Linux you should NOT use MIT-pthreads but install LinuxThreads!
...
@@ -5989,7 +5994,7 @@ Note that on Linux you should NOT use MIT-pthreads but install LinuxThreads!
If your system does not provide native thread support, you will need to
If your system does not provide native thread support, you will need to
build @strong{MySQL} using the MIT-pthreads package. This includes
build @strong{MySQL} using the MIT-pthreads package. This includes
most
FreeBSD systems, SunOS 4.x, Solaris 2.4 and earlier, and some others.
older
FreeBSD systems, SunOS 4.x, Solaris 2.4 and earlier, and some others.
@xref{Which OS}.
@xref{Which OS}.
@itemize @bullet
@itemize @bullet
...
@@ -22229,40 +22234,49 @@ Berkeley DB (@uref{http://www.sleepycat.com}) has provided
...
@@ -22229,40 +22234,49 @@ Berkeley DB (@uref{http://www.sleepycat.com}) has provided
crashes and also provides @code{COMMIT} and @code{ROLLBACK} on
crashes and also provides @code{COMMIT} and @code{ROLLBACK} on
transactions. In order to build MySQL Version 3.23.x (BDB support first
transactions. In order to build MySQL Version 3.23.x (BDB support first
appeared in Version 3.23.15) with support for @code{BDB} tables, you
appeared in Version 3.23.15) with support for @code{BDB} tables, you
will need Berkeley DB Version 3.
1.14
or newer which can be downloaded from
will need Berkeley DB Version 3.
2.3d
or newer which can be downloaded from
@uref{http://www.mysql.com/downloads/mysql-3.23.html}
; or also from
@uref{http://www.mysql.com/downloads/mysql-3.23.html}
. This is a patched
Sleepycat's download page at
version of Berkeley DB that is only available from @strong{MySQL}; the
@uref{http://www.sleepycat.com/download.html
}.
standard Berkeley DB @strong{will not work with MySQL
}.
@node BDB install, BDB start, BDB overview, BDB
@node BDB install, BDB start, BDB overview, BDB
@subsection Installing BDB
@subsection Installing BDB
To install Berkeley DB, first uncompress the @code{BDB} distribution
If you have downloaded a binary version of @strong{MySQL} that includes
and follow the instructions in the README file provided in the distribution
support for Berkeley DB, simply follow the instructions for
directory. Basically what you need to do is:
installing a binary version of @strong{MySQL}. @xref{Installing binary}.
To compile MySQL with Berkeley DB support, first uncompress the
@code{BDB} distribution into the @strong{MySQL} top-level source
directory, and follow the instructions for building MySQL from
source. Configure will automatically detect and use the Berkeley
DB source you just uncompressed. @xref{Installing source}.
@example
@example
cd build_[your_os]
cd /path/to/source/of/mysql-3.23.29-gamma
../dist/configure
gzip -cd /tmp/db-3.2.3d.tar.gz | tar xf -
make
./configure # this will use Berkeley DB automatically
make install
@end example
@end example
Please refer to the manual provided by @code{BDB} distribution for
If you would like to install Berkeley DB separately, to use with
more/updated information.
other applications and MySQL, this is possible. Follow the directions
for installing Berkeley DB in the Berkeley DB README file. Then, pass
After this you need to configure your @strong{MySQL} with
the @code{--with-berkeley-db=DIR} option to @code{MySQL}'s @code{configure},
@code{--with-berkeley-db=DIR}. The directory is the one where you installed
where @code{DIR} refers to the installation prefix used when installing
@code{BDB} binaries with @code{make install}. (Usually
it is
Berkeley DB (by default
it is
/usr/local/BerkeleyDB.3.
1/.)
You can give additional options to
/usr/local/BerkeleyDB.3.
2).
You can give additional options to
@strong{MySQL} configure, @code{--with-berkeley-db-includes=DIR} and
@strong{MySQL} configure, @code{--with-berkeley-db-includes=DIR} and
@code{--with-berkeley-db-libs=DIR}, if the @code{BDB} includes and/or libs
@code{--with-berkeley-db-libs=DIR}, if the @code{BDB} includes and/or libs
directory is not under the first directory (by default they are).
directory is not under the first directory (by default they are).
Then complete the @strong{MySQL} installation as normal.
Then complete the @strong{MySQL} installation as normal.
Even if Berkeley DB is in itself very tested and reliable, the
Please refer to the manual provided by @code{BDB} distribution for
@strong{MySQL} interface is still very alpha, but we are actively
more/updated information.
improving and optimizing it to get it this stable real soon.
Even though Berkeley DB is in itself very tested and reliable,
the @strong{MySQL} interface is still considered beta quality.
We are actively improving and optimizing it to get it stable very
soon.
@node BDB start, BDB characteristic, BDB install, BDB
@node BDB start, BDB characteristic, BDB install, BDB
@subsection BDB startup options
@subsection BDB startup options
...
@@ -22271,6 +22285,12 @@ If you are running with @code{AUTOCOMMIT=0} then your changes in @code{BDB}
...
@@ -22271,6 +22285,12 @@ If you are running with @code{AUTOCOMMIT=0} then your changes in @code{BDB}
tables will not be updated until you execute @code{COMMIT}. Instead of commit
tables will not be updated until you execute @code{COMMIT}. Instead of commit
you can execute @code{ROLLBACK} to forget your changes. @xref{COMMIT}.
you can execute @code{ROLLBACK} to forget your changes. @xref{COMMIT}.
If you are running with @code{AUTOCOMMIT=1} (the default), your changes
will be committed immediately. You can start an extended transaction with
the @code{BEGIN WORK} SQL command, after which your changes will not be
committed until you execute @code{COMMIT} (or decide to @code{ROLLBACK}
the changes).
The following options to @code{mysqld} can be used to change the behavior of
The following options to @code{mysqld} can be used to change the behavior of
BDB tables:
BDB tables:
...
@@ -22283,6 +22303,7 @@ BDB tables:
...
@@ -22283,6 +22303,7 @@ BDB tables:
@item @code{--bdb-recover} @tab Start Berkeley DB in recover mode.
@item @code{--bdb-recover} @tab Start Berkeley DB in recover mode.
@item @code{--bdb-tmpdir=directory} @tab Berkeley DB tempfile name.
@item @code{--bdb-tmpdir=directory} @tab Berkeley DB tempfile name.
@item @code{--skip-bdb} @tab Don't use berkeley db.
@item @code{--skip-bdb} @tab Don't use berkeley db.
@item @code{-O bdb_lock_max=1000} @tab Set the maximum number of locks possible. @xref{SHOW VARIABLES}.
@end multitable
@end multitable
If you use @code{--skip-bdb}, @strong{MySQL} will not initialize the
If you use @code{--skip-bdb}, @strong{MySQL} will not initialize the
...
@@ -22335,15 +22356,16 @@ read may fail with a deadlock error.
...
@@ -22335,15 +22356,16 @@ read may fail with a deadlock error.
@item
@item
Keys are not compressed to previous keys as with ISAM or MyISAM
Keys are not compressed to previous keys as with ISAM or MyISAM
tables. In other words, the key information will take a little more
tables. In other words, the key information will take a little more
space in @code{BDB} tables compared to MyISAM tables w
it
h don't use
space in @code{BDB} tables compared to MyISAM tables w
hic
h don't use
@code{PACK_KEYS=0}.
@code{PACK_KEYS=0}.
@item
@item
One must do a @code{FLUSH LOGS} from time to time to sync to get checkpoints
@strong{MySQL} performs a checkpoint each time a new Berkeley DB log
for the @code{BDB} tables.
file is started, and removes any log files that are not needed for
@item
current transactions. One can also run @code{FLUSH LOGS} at any time
As transaction logs take up more space than ordinary logs, it's more important
to checkpoint the Berkeley DB tables.
to rotate and remove old logs when using @code{BDB} tables than when using other table
types.
For disaster recovery, one should use table backups plus MySQL's binary
log. @xref{Backup}.
@end itemize
@end itemize
@node BDB TODO, BDB errors, BDB characteristic, BDB
@node BDB TODO, BDB errors, BDB characteristic, BDB
...
@@ -22369,8 +22391,9 @@ error file:
...
@@ -22369,8 +22391,9 @@ error file:
001119 23:43:56 bdb: txn_abort: Log undo failed for LSN: 1 3644744: Invalid
001119 23:43:56 bdb: txn_abort: Log undo failed for LSN: 1 3644744: Invalid
@end example
@end example
This is not fatal but we don't recommend you to delete tables you are
This is not fatal but we don't recommend that you delete tables if you are
using in not @code{auto_commit} mode.
not in @code{auto_commit} mode, until this problem is fixed (the fix is
not trivial).
@cindex tutorial
@cindex tutorial
@cindex terminal monitor, defined
@cindex terminal monitor, defined
...
@@ -38905,6 +38928,9 @@ though, so Version 3.23 is not released as a stable version yet.
...
@@ -38905,6 +38928,9 @@ though, so Version 3.23 is not released as a stable version yet.
@appendixsubsec Changes in release 3.23.29
@appendixsubsec Changes in release 3.23.29
@itemize @bullet
@itemize @bullet
@item
@item
Automatically remove Berkeley DB transaction logs that are no longer in
use.
@item
Changed crash-me and the MySQL benchmarks to also work with FrontBase.
Changed crash-me and the MySQL benchmarks to also work with FrontBase.
@item
@item
Allow @code{RESTRICT} and @code{CASCADE} after @code{DROP TABLE} to make
Allow @code{RESTRICT} and @code{CASCADE} after @code{DROP TABLE} to make
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