List:Commits« Previous MessageNext Message »
From:john.russell Date:March 21 2011 6:52pm
Subject:svn commit - mysqldoc@oter02: r25463 - trunk/dynamic-docs/glossary
View as plain text  
Author: jdrussel
Date: 2011-03-21 19:52:18 +0100 (Mon, 21 Mar 2011)
New Revision: 25463

Log:
Introduce a couple of commented-out terms, clarify some others.
Based on terminology for latest InnoDB presentations.


Modified:
   trunk/dynamic-docs/glossary/innodb.xml


Modified: trunk/dynamic-docs/glossary/innodb.xml
===================================================================
--- trunk/dynamic-docs/glossary/innodb.xml	2011-03-21 17:14:34 UTC (rev 25462)
+++ trunk/dynamic-docs/glossary/innodb.xml	2011-03-21 18:52:18 UTC (rev 25463)
Changed blocks: 8, Lines Added: 72, Lines Deleted: 3; 3856 bytes

@@ -1425,12 +1425,21 @@
         <emphasis role="bold">transaction</emphasis>; they cannot be
         <emphasis role="bold">rolled back</emphasis>.
       </para>
+      <para>
+        The InnoDB-related aspects of DDL include speed improvements for
+        <literal role="stmt">CREATE INDEX</literal> and
+        <literal role="stmt">DROP INDEX</literal> statements, and the
+        way the <emphasis role="bold">file-per-table</emphasis> setting
+        affects the behaviour of the <literal role="stmt">TRUNCATE
+        TABLE</literal> statement.
+      </para>
 
     </def>
     <gseealso glosid="sql"/>
     <gseealso glosid="transaction"/>
     <gseealso glosid="commit"/>
     <gseealso glosid="rollback"/>
+    <gseealso glosid="file_per_table"/>
 
   </glossent>
 

@@ -2238,6 +2247,18 @@
 
   </glossent>
 
+<!--
+<glossent id="futex">
+<gterm>futex</gterm>
+<def>
+<para>
+Linux-specific.
+</para>
+</def>
+<gseealso glosid="mutex"/>
+</glossent>
+-->
+
   <glossent id="ga">
 
     <gterm>GA</gterm>

@@ -2286,6 +2307,18 @@
 
   </glossent>
 
+<!--
+<glossent id="green_mutex">
+<gterm>green mutex</gterm>
+<def>
+<para>
+</para>
+</def>
+<gseealso glosid="mutex"/>
+<gseealso glosid="pthread"/>
+</glossent>
+-->
+
   <glossent id="group_commit">
 
     <gterm>group commit</gterm>

@@ -2486,7 +2519,7 @@
 
       <para>
         The actual name of the <emphasis role="bold">schema</emphasis>
-        that contains the <emphasis role="bold">data
+        that contains the MySQL <emphasis role="bold">data
         dictionary</emphasis>. To examine information (metadata) about
         the database, you can query tables such as
         <literal>INFORMATION_SCHEMA.TABLES</literal> and

@@ -2502,8 +2535,9 @@
         with performance monitoring, tuning, and troubleshooting. In
         particular, these tables provide information about the InnoDB
         features related to
-        <emphasis role="bold">compression</emphasis>, and transactions
-        and their associated locks.
+        <emphasis role="bold">compression</emphasis>, and
+        <emphasis role="bold">transactions</emphasis> and their
+        associated <emphasis role="bold">locks</emphasis>.
       </para>
 
     </def>

@@ -3580,6 +3614,18 @@
 
   </glossent>
 
+<!--
+<glossent id="metrics_counter">
+<gterm>metrics counter</gterm>
+<def>
+<para>
+</para>
+</def>
+<gseealso glosid="information_schema"/>
+<gseealso glosid="performance_schema"/>
+</glossent>
+-->
+
   <glossent id="mrg_file">
 
     <gterm>.MRG file</gterm>

@@ -3860,6 +3906,11 @@
         access. Mutexes and rw-locks are known collectively as
         <emphasis role="bold">latches</emphasis>.
       </para>
+<!--
+			<para>
+			This and related terms are appropriate for expert-level tuning and troubleshooting, or developing MySQL add-ons and monitoring tools.
+			</para>
+-->
 
     </def>
     <gseealso glosid="pthreads"/>

@@ -4068,6 +4119,24 @@
 
   </glossent>
 
+<!--
+<glossent id="online">
+<gterm></gterm>
+<def>
+<para>
+A type of operation that involves no downtime, blocking, or restricted operation for the database.
+Typically applied to <emphasis role="bold">DDL</emphasis>. Operations that shorten the periods of
+restricted operation, such as <emphasis role="bold">fast index creation</emphasis>, are a step along the way to true online DDL.
+A <emphasis role="bold">hot backup</emphasis> is an online operation and a <emphasis role="bold">warm backup</emphasis> is partially an online operation.
+</para>
+</def>
+<gseealso glosid="ddl"/>
+<gseealso glosid="fast_index_creation"/>
+<gseealso glosid="hot_backup"/>
+<gseealso glosid="warm_backup"/>
+</glossent>
+-->
+
   <glossent id="opt_file">
 
     <gterm>.OPT file</gterm>


Thread
svn commit - mysqldoc@oter02: r25463 - trunk/dynamic-docs/glossaryjohn.russell21 Mar