bk commit - mysqldoc@docsrva tree (heikki:1.2736)

[Heikki Tuuri]

Below is the list of changes that have just been committed into a local
mysqldoc repository of heikki. When heikki 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.2736 05/06/01 18:03:34 heikki@stripped +1 -0
  manual.texi:
    Add missing InnoDB change notes to 4.1.12, 4.1.13, 5.0.6, 5.0.7

  Docs/manual.texi
    1.2970 05/06/01 18:02:02 heikki@stripped +33 -3
    Add missing InnoDB change notes to 4.1.12, 4.1.13, 5.0.6, 5.0.7

# 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:	heikki
# Host:	hundin.mysql.fi
# Root:	/home/heikki/bk

--- 1.2969/Docs/manual.texi	Wed Jun  1 09:51:58 2005
+++ 1.2970/Docs/manual.texi	Wed Jun  1 18:02:02 2005
@@ -100405,14 +100405,15 @@
 sometimes triggered a memory deallocation bug on Windows resulting in a
 server crash.  (Bug #9593)
 @item
-@code{InnoDB}: In @code{DROP DATABASE}, check for all referencing tables
-from other databases before dropping any tables.  (Bug #10335)
-@item
 @code{InnoDB}: Do very fast shutdown only if @code{innodb_fast_shutdown=2},
 but wait for threads to exit and release allocated memory if
 @code{innodb_fast_shutdown=1}.  Starting with MySQL/InnoDB 5.0.5, InnoDB
 would do brutal shutdown also when @code{innodb_fast_shutdown=1}.  (Bug #9673)
 @item
+@code{InnoDB}: Fixed @code{InnoDB: Error: stored_select_lock_type is
+0 inside ::start_stmt()!} in a stored procedure call if
+@code{innodb_locks_unsafe_for_binlog} was set in @file{my.cnf}.  (Bug #10746)
+@item
 Fixed a server crash for @code{INSERT} or @code{UPDATE} when the @code{WHERE}
 clause contained a correlated subquery that referred to a column of the table
 being modified.  (Bug #6384)
@@ -100694,6 +100695,11 @@
 Fixed a problem with mishandling of @code{NULL} key parts in hash indexes on
 @code{VARCHAR} columns, resulting in incorrect query results.  (Bug #9489,
 Bug #10176)
+@item
+@code{InnoDB}: Fixed a critical bug in InnoDB @code{AUTO_INCREMENT}: it
+could assign the same value for several rows.  (Bug #10359)
+@code{InnoDB}: All InnoDB bug fixes from 4.1.12 and earlier versions, and also
+the fixes to bugs #10335 and #10607 listed in the 4.1.13 change notes.
 @end itemize
 
 @node News-5.0.5, News-5.0.4, News-5.0.6, News-5.0.x
@@ -102396,6 +102402,10 @@
 @code{InnoDB}: In @code{DROP DATABASE}, check for all referencing tables
 from other databases before dropping any tables.  (Bug #10335)
 @item
+@code{InnoDB}: Fix bug: InnoDB wrongly complained in the 
+@file{.err} log that MySQL is trying to drop a non-existent table, if
+tablespace ran out.  (Bug #10607)
+@item
 Fixed an overly strict debugging assertion that caused debug server
 builds to fail for some @code{@var{col_name} = @var{const_expr}}, where
 @var{const_expr} was a constant expression such as a subquery.  (Bug #10020)
@@ -102698,6 +102708,26 @@
 @code{InnoDB}: Fixed a deadlock without any locking, simple select and
 update. (Bug #7975) @code{InnoDB} now takes an exclusive lock
 when @code{INSERT ON DUPLICATE KEY UPDATE} is checking duplicate keys.
+@item
+@code{InnoDB}: Fix a problem in crash recovery of @file{.ibd} files on
+Windows if the user used @code{lower_case_table_names=0} or @code{2};
+the directory scan in crash recovery forgot to put all paths to lower case,
+so that the tablespace name would be consistent with the internal data
+dictionary of InnoDB.
+@item
+@code{InnoDB}: Add fault tolerance in the scan of @file{.ibd} files at a
+crash recovery; formerly a single failure of @code{readdir_get_next}
+caused the rest of the directory to be skipped.
+@item
+@code{InnoDB}: Fix assertion failures of type
+@code{ut_a(cursor->old_stored == BTR_PCUR_OLD_STORED)}
+and @code{prebuilt->template_type == 0}.
+This bug was introduced in 4.1.10 and 4.0.24.  (Bug #9670)
+@item
+@code{InnoDB}: Fix a performance bug:
+At the shutdown, write the latest lsn only to the first pages of the
+@file{ibdata} files of the system tablespace, NOT to the @file{.ibd} files;
+writing to tens of thousands @file{.ibd} files can take minutes.
 @item
 Fix for auto-increment not working with @code{INSERT..SELECT} and NDB storage
 engine. (Bug #9675)