bk commit - mysqldoc tree (guilhem:1.2881)

[guilhem]

Below is the list of changes that have just been committed into a local
mysqldoc repository of guilhem. When guilhem 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.2881 05/04/19 10:45:23 guilhem@stripped +1 -0
  documenting changes to innodb_fast_shutdown in 5.0.5 (now settable on the fly, and value
of 2 does a crash-like InnoDB shutdown)

  Docs/manual.texi
    1.2711 05/04/19 10:45:15 guilhem@stripped +15 -3
    documenting changes to innodb_fast_shutdown in 5.0.5.

# 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:	guilhem
# Host:	gbichot2.local
# Root:	/home/mysql_src/mysqldoc

--- 1.2710/Docs/manual.texi	2005-04-18 19:22:26 +02:00
+++ 1.2711/Docs/manual.texi	2005-04-19 10:45:15 +02:00
@@ -20433,7 +20433,7 @@
 | innodb_buffer_pool_size         | 8388608                                              
      |
 | innodb_data_file_path           | ibdata1:10M:autoextend                               
      |
 | innodb_data_home_dir            |                                                      
      |
-| innodb_fast_shutdown            | ON                                                   
      |
+| innodb_fast_shutdown            | 1                                                    
     |
 | innodb_file_io_threads          | 4                                                    
      |
 | innodb_file_per_table           | OFF                                                  
      |
 | innodb_locks_unsafe_for_binlog  | OFF                                                  
      |
@@ -22785,7 +22785,8 @@
 
 Each storage engine performs any actions necessary for tables that it manages.
 For example, MyISAM flushes any pending index writes for a table.
-InnoDB flushes its buffer pool to disk, writes the current LSN to the
+InnoDB flushes its buffer pool to disk (starting from 5.0.5: unless
+@code{innodb_fast_shutdown} is 2), writes the current LSN to the
 tablespace, and terminates its own internal threads.
 
 @item
@@ -67213,7 +67214,11 @@
 buffer merge before a shutdown. These operations can take minutes,
 or even hours in extreme cases.  If you set this parameter to 1, @code{InnoDB}
 skips these operations at shutdown. The default value is 1 starting
-from 3.23.50.
+from 3.23.50. If you set it to 2 (available starting from MySQL 5.0.5, except
+on Netware) InnoDB will just flush its logs and then shut down brutally (and
+fastly) like if it was a MySQL crash; no committed transaction will be lost,
+but a crash recovery will be done at next startup.
+
 
 @item innodb_file_io_threads
 The number of file I/O threads in @code{InnoDB}. Normally this should be
@@ -99184,6 +99189,13 @@
 
 Functionality added or changed:
 @itemize @bullet
+@item
+@code{--innodb-fast-shutdown} is now also settable on the fly (global variable
+@code{innodb_fast_shutdown}). It now accepts values 0, 1 and 2 (except on
+Netware where 2 is disabled); if set to 2, then when the MySQL server shuts
+down, InnoDB will just flush its logs and then shut down brutally (and fastly)
+like if it was a MySQL crash; no committed transaction will be lost, but a
+crash recovery will be done at next startup.
 @end itemize
 
 Bugs fixed: