@@ -23136,7 +23136,7 @@ you start using MySQL in a production environment, you can
remove the @code{-l} option from @code{mysql.server} or change it to
@code{--log-bin}.
The entries in this log are written as @code{mysqld} receives the questions.
The entries in this log are written as @code{mysqld} receives the queries.
This may be different from the order in which the statements are executed.
This is in contrast to the update log and the binary log which are written
after the query is executed, but before any locks are released.
...
...
@@ -23149,7 +23149,7 @@ after the query is executed, but before any locks are released.
@cindex files, update log
@strong{Note}: the update log is replaced by the binary
log. @xref{Binary log}. With this you can do anything that you can do
log. @xref{Binary log}. You can do anything with the binary log that you can do
with the update log.
When started with the @code{--log-update[=file_name]} option,
...
...
@@ -23164,7 +23164,7 @@ flush-logs}, execute the @code{FLUSH LOGS} statement, or restart the server.
@strong{Note}: for the above scheme to work, you must not create
your own files with the same filename as the update log + some extensions
that may be regarded as a number, in the directory used by the update log!
that may be regarded as a number in the directory used by the update log!
If you use the @code{--log} or @code{-l} options, @code{mysqld} writes a
general log with a filename of @file{hostname.log}, and restarts and
...
...
@@ -23208,8 +23208,8 @@ and the crash.
@cindex binary log
@cindex files, binary log
The intention is that the binary log should replace the update log, so
we recommend you to switch to this log format as soon as possible!
The binary log will replace the now deprecated update log, so
we recommend you to switch to this log format as soon as possible.
The binary log contains all information that is available in the update
log in a more efficient format. It also contains information about how long
...
...
@@ -23218,10 +23218,10 @@ every query that updated the database took.
The binary log is also used when you are replicating a slave from a master.
@xref{Replication}.
When started with the @code{--log-bin[=file_name]} option, @code{mysqld}
When started with the @code{--log-bin[=file_name]} option @code{mysqld}
writes a log file containing all SQL commands that update data. If no
file name is given, it defaults to the name of the host machine followed
by @code{-bin}. If file name is given, but it doesn't contain a path, the
file name is given it defaults to the name of the host machine followed
by @code{-bin}. If a file name is given, but doesn't contain a path, the
file is written in the data directory.
If you supply an extension to @code{--log-bin=filename.extension}, the
...
...
@@ -23241,14 +23241,9 @@ to the binary log:
@multitable @columnfractions .38 .62
@item @strong{Option} @tab @strong{Description}
@item @code{binlog-do-db=database_name} @tab
Tells the master it should log updates for the specified database, and
exclude all others not explicitly mentioned.
(Example: @code{binlog-do-db=some_database})
@item @code{binlog-do-db=database_name} @tab Tells the master it should log updates for the specified database, and exclude all others not explicitly mentioned. (Example: @code{binlog-do-db=some_database})
@item @code{binlog-ignore-db=database_name} @tab
Tells the master that updates to the given database should not be logged
to the binary log (Example: @code{binlog-ignore-db=some_database})
@item @code{binlog-ignore-db=database_name} @tab Tells the master that updates to the given database should not be logged to the binary log (Example: @code{binlog-ignore-db=some_database})
@end multitable
To be able to know which different binary log files have been used,
...
...
@@ -23272,10 +23267,10 @@ mysqlbinlog log-file | mysql -h server_name
@end example
You can also use the @code{mysqlbinlog} program to read the binary log
directly from a remote MySQL server!
directly from a remote MySQL server.
@code{mysqlbinlog --help} will give you more information of how to use
this program!
this program.
If you are using @code{BEGIN [WORK]} or @code{SET AUTOCOMMIT=0}, you must
use the MySQL binary log for backups instead of the old update log.
...
...
@@ -23284,10 +23279,10 @@ The binary logging is done immediately after a query completes but before
any locks are released or any commit is done. This ensures that the log
will be logged in the execution order.
All updates (@code{UPDATE}, @code{DELETE} or @code{INSERT}) that change
a transactional table (like BDB tables) are cached until a @code{COMMIT}.
Any updates to a non-transactional table are stored in the binary log at
once. Every thread will, on start, allocate a buffer of
once. All updates (@code{UPDATE}, @code{DELETE} or @code{INSERT}) that change
a transactional table (like BDB tables) are cached until a @code{COMMIT}.
Every thread will, on start, allocate a buffer of
@code{binlog_cache_size} to buffer queries. If a query is bigger than
this, the thread will open a temporary file to handle the bigger cache.
The temporary file will be deleted when the thread ends.
...
...
@@ -23313,10 +23308,10 @@ more than @code{long_query_time} to execute. The time to get the initial
table locks are not counted as execution time.
The slow query log is logged after the query is executed and after all
locks has been released. This may be different from the order in which
locks have been released. This may be different from the order in which
the statements are executed.
If no filename is given, it defaults to the name of the host machine
If no filename is given, it defaults to the name of the host machine
suffixed with @code{-slow.log}. If a filename is given, but doesn't
contain a path, the file is written in the data directory.
...
...
@@ -23326,8 +23321,8 @@ can become a difficult task. You can pipe the slow query log through the
@code{mysqldumpslow} command to get a summary of the queries which
appear in the log.
You are using @code{--log-long-format} then also queries that are not
using indexes are printed. @xref{Command-line options}.
If you use @code{--log-long-format} also, then queries that do not
use indexes are logged as well. @xref{Command-line options}.
