List:Commits« Previous MessageNext Message »
From:john.russell Date:December 8 2010 11:07pm
Subject:svn commit - mysqldoc@docsrva: r24341 - trunk/dynamic-docs/glossary
View as plain text  
Author: jrussell
Date: 2010-12-09 00:07:03 +0100 (Thu, 09 Dec 2010)
New Revision: 24341

Log:
Add a glossary entry for SSD.
Also move one other entry into better alphabetical order, just for convenience
in editing.


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


Modified: trunk/dynamic-docs/glossary/innodb.xml
===================================================================
--- trunk/dynamic-docs/glossary/innodb.xml	2010-12-08 20:51:33 UTC (rev 24340)
+++ trunk/dynamic-docs/glossary/innodb.xml	2010-12-08 23:07:03 UTC (rev 24341)
Changed blocks: 3, Lines Added: 49, Lines Deleted: 25; 3087 bytes

@@ -2248,6 +2248,12 @@
         <emphasis role="bold">commit</emphasis> operations, rather than
         flushing and syncing separately for each commit.
       </para>
+      <para>
+        In a replication context, with the <emphasis role="bold">binary
+        log</emphasis> enabled, set the configuration option
+        <literal>sync_binlog=0</literal> to keep the binary log in synch
+        with InnoDB transaction order during group commit operations.
+      </para>
 
     </def>
     <gseealso glosid="commit" />

@@ -5281,31 +5287,6 @@
 
   </glossent>
 
-  <glossent id="strict_mode">
-
-    <gterm>strict mode</gterm>
-    <def>
-
-      <para>
-        The general name for the setting controlled by the
-        <literal>innodb_strict_mode</literal> option. Turning on this
-        setting causes certain conditions that are normally treated as
-        warnings, to be considered errors. For example, certain invalid
-        combinations of options related to <emphasis role="bold">file
-        format</emphasis> and <emphasis role="bold">row
-        format</emphasis>, that normally produce a warning and continue
-        with default values, now cause the <literal>CREATE
-        TABLE</literal> operation to fail.
-      </para>
-      <para>
-        MySQL also has something called strict mode.
-      </para>
-
-    </def>
-    <gseealso glosid="innodb_strict_mode" />
-
-  </glossent>
-
   <glossent id="shutdown">
 
     <gterm>shutdown</gterm>

@@ -5357,6 +5338,49 @@
 
   </glossent>
 
+  <glossent id="ssd">
+
+    <gterm>SSD</gterm>
+    <def>
+
+      <para>
+        Acronym for <quote>solid-state drive</quote>. A type of storage
+        device with different performance characteristics than a
+        traditional hard drive: smaller storage capacity, faster for
+        random reads, no moving parts, and with a number of
+        considerations affecting write performance.
+      </para>
+
+    </def>
+    <gseealso glosid="disk_based" />
+
+  </glossent>
+
+  <glossent id="strict_mode">
+
+    <gterm>strict mode</gterm>
+    <def>
+
+      <para>
+        The general name for the setting controlled by the
+        <literal>innodb_strict_mode</literal> option. Turning on this
+        setting causes certain conditions that are normally treated as
+        warnings, to be considered errors. For example, certain invalid
+        combinations of options related to <emphasis role="bold">file
+        format</emphasis> and <emphasis role="bold">row
+        format</emphasis>, that normally produce a warning and continue
+        with default values, now cause the <literal>CREATE
+        TABLE</literal> operation to fail.
+      </para>
+      <para>
+        MySQL also has something called strict mode.
+      </para>
+
+    </def>
+    <gseealso glosid="innodb_strict_mode" />
+
+  </glossent>
+
   <glossent id="sublist">
 
     <gterm>sublist</gterm>


Thread
svn commit - mysqldoc@docsrva: r24341 - trunk/dynamic-docs/glossaryjohn.russell9 Dec