Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html
ChangeSet
1.2516 04/12/21 09:26:23 paul@stripped +2 -0
manual.texi:
Add an option to InnoDB startup option list.
Add entries to list of dynamic system variables.
renamed-nodes.txt:
Fix capitalization.
Remap a too-generic node name.
Docs/manual.texi
1.2279 04/12/21 09:25:49 paul@stripped +22 -8
Add an option to InnoDB startup option list.
Add entries to list of dynamic system variables.
Docs/renamed-nodes.txt
1.20 04/12/21 09:15:06 paul@stripped +1 -1
Fix capitalization.
Docs/renamed-nodes.txt
1.19 04/12/21 09:14:07 paul@stripped +1 -0
Remap a too-generic node name.
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: paul
# Host: frost.snake.net
# Root: /Volumes/frost2/MySQL/bk/mysqldoc
--- 1.2278/Docs/manual.texi 2004-12-20 18:47:06 -06:00
+++ 1.2279/Docs/manual.texi 2004-12-21 09:25:49 -06:00
@@ -21378,6 +21378,10 @@
@item @code{ft_boolean_syntax} @tab numeric @tab @code{GLOBAL}
@item @code{group_concat_max_len} @tab numeric @tab @code{GLOBAL} | @code{SESSION}
@item @code{identity} @tab numeric @tab @code{SESSION}
+@c innodb_autoextend_increment: introduced in 4.1.5, made settable in 4.1.6
+@item @code{innodb_autoextend_increment} @tab numeric @tab @code{GLOBAL}
+@item @code{innodb_max_purge_lag} @tab numeric @tab @code{GLOBAL}
+@item @code{innodb_table_locks} @tab boolean @tab @code{GLOBAL} | @code{SESSION}
@item @code{insert_id} @tab boolean @tab @code{SESSION}
@item @code{interactive_timeout} @tab numeric @tab @code{GLOBAL} | @code{SESSION}
@item @code{join_buffer_size} @tab numeric @tab @code{GLOBAL} | @code{SESSION}
@@ -64392,7 +64396,7 @@
* Moving:: Moving an @code{InnoDB} Database to Another Machine
* InnoDB transaction model:: @code{InnoDB} Transaction Model and Locking
* InnoDB tuning:: @code{InnoDB} Performance Tuning Tips
-* Implementation:: Implementation of Multi-Versioning
+* InnoDB Multi-Versioning:: Implementation of Multi-Versioning
* Table and index:: Table and Index Structures
* File space management:: File Space Management and Disk I/O
* InnoDB Error handling:: Error Handling
@@ -64890,7 +64894,8 @@
@item innodb_autoextend_increment
The increment size (in megabytes) for extending the size of an autoextending
tablespace when it becomes full. The default value is 8.
-This option is available starting from MySQL 4.1.5.
+This option is available starting from MySQL 4.1.5. As of MySQL 4.1.6, it
+can be changed at runtime as a global system variable.
@item innodb_buffer_pool_awe_mem_mb
The size of the buffer pool (in MB), if it is placed in the AWE memory of
@@ -65142,6 +65147,15 @@
SET GLOBAL innodb_max_dirty_pages_pct = @var{value};
@end example
+@item innodb_max_purge_lag
+This option controls how to delay @code{INSERT}, @code{UPDATE}
+and @code{DELETE} operations when the purge operations are lagging.
+The default value of this parameter is zero, meaning that there will
+not be any delays. When the value is greater than zero, @code{InnoDB}
+may delay new row operations, as described in @ref{InnoDB Multi-Versioning}.
+This option can be changed at runtime as a global system variable.
+@code{innodb_max_purge_lag} is available as of MySQL 4.0.22 and 4.1.6.
+
@item innodb_mirrored_log_groups
The number of identical copies of log groups we keep for the
database. Currently this should be set to 1.
@@ -66971,7 +66985,7 @@
@end itemize
-@node InnoDB tuning, Implementation, InnoDB transaction model, InnoDB
+@node InnoDB tuning, InnoDB Multi-Versioning, InnoDB transaction model, InnoDB
@section @code{InnoDB} Performance Tuning Tips
@itemize @bullet
@@ -67402,7 +67416,7 @@
if the configuration option @code{innodb_status_file=1} is set.
-@node Implementation, Table and index, InnoDB tuning, InnoDB
+@node InnoDB Multi-Versioning, Table and index, InnoDB tuning, InnoDB
@section Implementation of Multi-Versioning
Because @code{InnoDB} is a multi-versioned database, it must keep information
@@ -67467,7 +67481,7 @@
Starting with MySQL/InnoDB-4.1.6 and 4.0.22, there is a startup option
and settable global variable @code{innodb_max_purge_lag}, which is
-zero by default. When this parameter is nonzero, InnoDB may delay new
+zero by default. When this parameter is non-zero, InnoDB may delay new
row operations. When the @var{purge_lag} exceeds
@code{innodb_max_purge_lag}, each @code{INSERT}, @code{UPDATE} and
@code{DELETE} operation will be delayed by
@@ -67479,7 +67493,7 @@
million, assuming that our transactions are small, only 100 bytes in
size, and we can allow @w{100 MB} of unpurged rows in our tables.
-@node Table and index, File space management, Implementation, InnoDB
+@node Table and index, File space management, InnoDB Multi-Versioning, InnoDB
@section Table and Index Structures
MySQL stores its data dictionary information for tables in @file{.frm}
@@ -94582,7 +94596,7 @@
@code{innodb_max_purge_lag} for delaying @code{INSERT}, @code{UPDATE}
and @code{DELETE} operations when the purge operations are lagging.
The default value of this parameter is zero, meaning that there will
-not be any delays. @xref{Implementation}.
+not be any delays. @xref{InnoDB Multi-Versioning}.
@item
InnoDB: The @code{innodb_autoextend_increment} startup option that was
introduced in release 4.1.5 was made a settable global variable. (Bug #5736)
@@ -96531,7 +96545,7 @@
@code{innodb_max_purge_lag} for delaying @code{INSERT}, @code{UPDATE}
and @code{DELETE} operations when the purge operations are lagging.
The default value of this parameter is zero, meaning that there will
-not be any delays. @xref{Implementation}.
+not be any delays. @xref{InnoDB Multi-Versioning}.
@item
InnoDB: Change error code to @code{HA_ERR_ROW_IS_REFERENCED} if we cannot
@code{DROP} a parent table because it is referenced by a
--- 1.18/Docs/renamed-nodes.txt 2004-11-18 12:39:52 -06:00
+++ 1.20/Docs/renamed-nodes.txt 2004-12-21 09:15:06 -06:00
@@ -51,3 +51,4 @@
bdb BDB_storage_engine
isam ISAM_storage_engine
reference Language_structure
+implementation InnoDB_Multi-Versioning
| Thread |
|---|
| • bk commit - mysqldoc tree (paul:1.2516) | paul | 21 Dec |
