bk commit - mysqldoc@docsrva tree (jon:1.2860)

[jon]

Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon 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.2860 05/06/23 13:12:12 jon@stripped +6 -0
  Updating InnoDB-5.0.8 news & bugfixes, InnoDB 
  concurrency checking. (Marko)
  Sync refman-4.1 and refman-5.0 with refman tree.

  refman/news.xml
    1.22 05/06/23 13:12:10 jon@stripped +32 -10
    InnoDB news and bugfixes. (Marko)

  refman/innodb.xml
    1.7 05/06/23 13:12:09 jon@stripped +5 -3
    Updated concurrency checking info. (Marko)

  refman-5.0/news.xml
    1.18 05/06/23 13:12:09 jon@stripped +32 -10
    Sync with refman.

  refman-5.0/innodb.xml
    1.3 05/06/23 13:12:09 jon@stripped +5 -3
    Sync with refman.

  refman-4.1/news.xml
    1.18 05/06/23 13:12:09 jon@stripped +32 -10
    Sync with refman.

  refman-4.1/innodb.xml
    1.3 05/06/23 13:12:08 jon@stripped +5 -3
    Synced with refman.

# 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:	jon
# Host:	gigan.site
# Root:	/home/jon/bk/mysqldoc

--- 1.2/refman-4.1/innodb.xml	2005-06-23 02:28:28 +10:00
+++ 1.3/refman-4.1/innodb.xml	2005-06-23 13:12:08 +10:00
@@ -1318,10 +1318,12 @@
     may have thread thrashing and should try setting this parameter
     lower or higher. If you have a computer with many processors and
     disks, you can try setting the value higher to better utilize the
-    resources of you computer. A recommended value is the sum of the
+    resources of your computer. A recommended value is the sum of the
     number of processors and disks your system has. A value of 500 or
     greater disables the concurrency checking. This option is available
-    starting from MySQL 3.23.44 and 4.0.1.
+    starting from MySQL 3.23.44 and 4.0.1. Starting with MySQL 5.0.8,
+    the default value is 20, and the concurrency checking will be disabled
+    if the setting is greater than or equal to 20.
    </para>
 
    <para>
@@ -4720,7 +4722,7 @@
      Contention can be due to heavy parallelism of queries, or problems
      in operating system thread scheduling. Setting
      <literal>innodb_thread_concurrency</literal> smaller than the
-     default value of <literal>8</literal> can help in such situations.
+     default value can help in such situations.
     </para></listitem>
 
     <listitem><para>

--- 1.17/refman-4.1/news.xml	2005-06-23 12:27:54 +10:00
+++ 1.18/refman-4.1/news.xml	2005-06-23 13:12:09 +10:00
@@ -513,6 +513,20 @@
      in an infinite timeout. (Bug #11290)
     </para></listitem>
 
+    <listitem>
+      <para><literal>InnoDB</literal>: Enforce maximum
+      <literal>CHAR_LENGTH()</literal> of UTF-8 data in <literal>ON
+      UPDATE CASCADE</literal>. (Bug #10409)
+      </para>
+    </listitem>
+
+    <listitem>
+      <para><literal>InnoDB</literal>: Pad UTF-8 variable-length
+      <literal>CHAR</literal> columns with
<literal>0x20</literal>. Pad
+      UCS2 <literal>CHAR</literal> columns with
+      <literal>0x0020</literal>. (Bug #10511)</para>
+    </listitem>
+
    </itemizedlist>
 
   </section>
@@ -4296,7 +4310,24 @@
      for prepared statements. (Bug #8367, Bug #9334)
     </para></listitem>
 
-   </itemizedlist>
+    <listitem>
+      <para><literal>InnoDB</literal>: Various optimizations. Removed
+      unreachable debug code from non-debug builds. Added hints for the
+      branch predictor in GCC. Made assertions occupy less space.</para>
+    </listitem>
+
+    <listitem>
+      <para><literal>InnoDB</literal>: Make
+      <literal>innodb_thread_concurrency=20</literal> by default. Bypass
+      the concurrency checking if the setting is greater than or equal
+      to 20.</para>
+    </listitem>
+
+    <listitem>
+      <para><literal>InnoDB</literal>: Make <literal>CHECK
+      TABLE</literal> killable. (Bug #9730)</para>
+    </listitem>
+  </itemizedlist>
 
    <para>
     Bugs fixed:
@@ -4476,15 +4507,6 @@
      Fixed a server crash resulting from <literal>CREATE TABLE ...
      SELECT</literal> that selected from a table being altered by
      <literal>ALTER TABLE</literal>. (Bug #10224)
-    </para></listitem>
-
-    <listitem><para>
-     Fixed server crash on Windows caused by <literal>USE
-     <replaceable>db_name</replaceable></literal> where
-     <replaceable>db_name</replaceable> is a Windows device name such as
-     <literal>LPT1</literal> or <literal>PRN</literal>.
-     (<ulink
url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink>)
-     (Bug #9148)
     </para></listitem>
 
     <listitem><para>

--- 1.2/refman-5.0/innodb.xml	2005-06-23 02:28:28 +10:00
+++ 1.3/refman-5.0/innodb.xml	2005-06-23 13:12:09 +10:00
@@ -1318,10 +1318,12 @@
     may have thread thrashing and should try setting this parameter
     lower or higher. If you have a computer with many processors and
     disks, you can try setting the value higher to better utilize the
-    resources of you computer. A recommended value is the sum of the
+    resources of your computer. A recommended value is the sum of the
     number of processors and disks your system has. A value of 500 or
     greater disables the concurrency checking. This option is available
-    starting from MySQL 3.23.44 and 4.0.1.
+    starting from MySQL 3.23.44 and 4.0.1. Starting with MySQL 5.0.8,
+    the default value is 20, and the concurrency checking will be disabled
+    if the setting is greater than or equal to 20.
    </para>
 
    <para>
@@ -4720,7 +4722,7 @@
      Contention can be due to heavy parallelism of queries, or problems
      in operating system thread scheduling. Setting
      <literal>innodb_thread_concurrency</literal> smaller than the
-     default value of <literal>8</literal> can help in such situations.
+     default value can help in such situations.
     </para></listitem>
 
     <listitem><para>

--- 1.17/refman-5.0/news.xml	2005-06-23 12:27:54 +10:00
+++ 1.18/refman-5.0/news.xml	2005-06-23 13:12:09 +10:00
@@ -513,6 +513,20 @@
      in an infinite timeout. (Bug #11290)
     </para></listitem>
 
+    <listitem>
+      <para><literal>InnoDB</literal>: Enforce maximum
+      <literal>CHAR_LENGTH()</literal> of UTF-8 data in <literal>ON
+      UPDATE CASCADE</literal>. (Bug #10409)
+      </para>
+    </listitem>
+
+    <listitem>
+      <para><literal>InnoDB</literal>: Pad UTF-8 variable-length
+      <literal>CHAR</literal> columns with
<literal>0x20</literal>. Pad
+      UCS2 <literal>CHAR</literal> columns with
+      <literal>0x0020</literal>. (Bug #10511)</para>
+    </listitem>
+
    </itemizedlist>
 
   </section>
@@ -4296,7 +4310,24 @@
      for prepared statements. (Bug #8367, Bug #9334)
     </para></listitem>
 
-   </itemizedlist>
+    <listitem>
+      <para><literal>InnoDB</literal>: Various optimizations. Removed
+      unreachable debug code from non-debug builds. Added hints for the
+      branch predictor in GCC. Made assertions occupy less space.</para>
+    </listitem>
+
+    <listitem>
+      <para><literal>InnoDB</literal>: Make
+      <literal>innodb_thread_concurrency=20</literal> by default. Bypass
+      the concurrency checking if the setting is greater than or equal
+      to 20.</para>
+    </listitem>
+
+    <listitem>
+      <para><literal>InnoDB</literal>: Make <literal>CHECK
+      TABLE</literal> killable. (Bug #9730)</para>
+    </listitem>
+  </itemizedlist>
 
    <para>
     Bugs fixed:
@@ -4476,15 +4507,6 @@
      Fixed a server crash resulting from <literal>CREATE TABLE ...
      SELECT</literal> that selected from a table being altered by
      <literal>ALTER TABLE</literal>. (Bug #10224)
-    </para></listitem>
-
-    <listitem><para>
-     Fixed server crash on Windows caused by <literal>USE
-     <replaceable>db_name</replaceable></literal> where
-     <replaceable>db_name</replaceable> is a Windows device name such as
-     <literal>LPT1</literal> or <literal>PRN</literal>.
-     (<ulink
url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink>)
-     (Bug #9148)
     </para></listitem>
 
     <listitem><para>

--- 1.6/refman/innodb.xml	2005-06-23 02:28:29 +10:00
+++ 1.7/refman/innodb.xml	2005-06-23 13:12:09 +10:00
@@ -1318,10 +1318,12 @@
     may have thread thrashing and should try setting this parameter
     lower or higher. If you have a computer with many processors and
     disks, you can try setting the value higher to better utilize the
-    resources of you computer. A recommended value is the sum of the
+    resources of your computer. A recommended value is the sum of the
     number of processors and disks your system has. A value of 500 or
     greater disables the concurrency checking. This option is available
-    starting from MySQL 3.23.44 and 4.0.1.
+    starting from MySQL 3.23.44 and 4.0.1. Starting with MySQL 5.0.8,
+    the default value is 20, and the concurrency checking will be disabled
+    if the setting is greater than or equal to 20.
    </para>
 
    <para>
@@ -4720,7 +4722,7 @@
      Contention can be due to heavy parallelism of queries, or problems
      in operating system thread scheduling. Setting
      <literal>innodb_thread_concurrency</literal> smaller than the
-     default value of <literal>8</literal> can help in such situations.
+     default value can help in such situations.
     </para></listitem>
 
     <listitem><para>

--- 1.21/refman/news.xml	2005-06-23 12:27:55 +10:00
+++ 1.22/refman/news.xml	2005-06-23 13:12:10 +10:00
@@ -513,6 +513,20 @@
      in an infinite timeout. (Bug #11290)
     </para></listitem>
 
+    <listitem>
+      <para><literal>InnoDB</literal>: Enforce maximum
+      <literal>CHAR_LENGTH()</literal> of UTF-8 data in <literal>ON
+      UPDATE CASCADE</literal>. (Bug #10409)
+      </para>
+    </listitem>
+
+    <listitem>
+      <para><literal>InnoDB</literal>: Pad UTF-8 variable-length
+      <literal>CHAR</literal> columns with
<literal>0x20</literal>. Pad
+      UCS2 <literal>CHAR</literal> columns with
+      <literal>0x0020</literal>. (Bug #10511)</para>
+    </listitem>
+
    </itemizedlist>
 
   </section>
@@ -4296,7 +4310,24 @@
      for prepared statements. (Bug #8367, Bug #9334)
     </para></listitem>
 
-   </itemizedlist>
+    <listitem>
+      <para><literal>InnoDB</literal>: Various optimizations. Removed
+      unreachable debug code from non-debug builds. Added hints for the
+      branch predictor in GCC. Made assertions occupy less space.</para>
+    </listitem>
+
+    <listitem>
+      <para><literal>InnoDB</literal>: Make
+      <literal>innodb_thread_concurrency=20</literal> by default. Bypass
+      the concurrency checking if the setting is greater than or equal
+      to 20.</para>
+    </listitem>
+
+    <listitem>
+      <para><literal>InnoDB</literal>: Make <literal>CHECK
+      TABLE</literal> killable. (Bug #9730)</para>
+    </listitem>
+  </itemizedlist>
 
    <para>
     Bugs fixed:
@@ -4476,15 +4507,6 @@
      Fixed a server crash resulting from <literal>CREATE TABLE ...
      SELECT</literal> that selected from a table being altered by
      <literal>ALTER TABLE</literal>. (Bug #10224)
-    </para></listitem>
-
-    <listitem><para>
-     Fixed server crash on Windows caused by <literal>USE
-     <replaceable>db_name</replaceable></literal> where
-     <replaceable>db_name</replaceable> is a Windows device name such as
-     <literal>LPT1</literal> or <literal>PRN</literal>.
-     (<ulink
url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0799">CAN-2005-0799</ulink>)
-     (Bug #9148)
     </para></listitem>
 
     <listitem><para>