Updated Changelog

@item @code{net_read_timeout}

Number of seconds to wait for more data from a connection before aborting

the read.  Note that when we don't expect data from a connection, the timeout

is defined by @code{write_timeout}.

is defined by @code{write_timeout}. See also @code{slave_read_timeout}.

@item @code{net_retry_count}

If a read on a communication port is interrupted, retry this many times

concerned about people being able to see what databases other users

have. See also @code{safe_show_databases}.

@item @code{slave_read_timeout}

Number of seconds to wait for more data from a master/slave connection

before aborting the read.

@item @code{slow_launch_time}

If creating the thread takes longer than this value (in seconds), the

@code{Slow_launch_threads} counter will be incremented.

@code{replicate-ignore-table=foo%.bar%} - will not upates to tables in all databases that start with foo and whose table names

start with bar)

@item @code{replicate-ignore-db=database_name} @tab

Tells the slave thread to not replicate to the specified database. To

specify more than one database to ignore, use the directive multiple

@code{replicate-wild-do-table=db_name.%}

(Example: @code{replicate-do-db=some_db})

@item @code{log-slave-updates} @tab

Tells the slave to log the updates from the slave thread to the binary

log. Off by default. You will need to turn it on if you plan to

@item @code{skip-slave-start} @tab

Tells the slave server not to start the slave on the startup.  The user

can start it later with @code{SLAVE START}.

@item @code{slave_read_timeout=#}

Number of seconds to wait for more data from the master before aborting

the read.

@end multitable

@cindex SQL commands, replication

@appendixsubsec Changes in release 3.23.40

@itemize @bullet

@item

Added @code{slave_wait_timeout} for replication.

@item

Fixed problem with @code{UPDATE} and BDB tables.

@item

Fixed problem when using the @code{GRANT FILE ON database.* ...}; Previously