List:Commits« Previous MessageNext Message »
From:john.russell Date:January 12 2011 4:05pm
Subject:svn commit - mysqldoc@docsrva: r24782 - trunk/dynamic-docs/glossary
View as plain text  
Author: jrussell
Date: 2011-01-12 17:05:14 +0100 (Wed, 12 Jan 2011)
New Revision: 24782

Log:
Added glossary entry for "torn page".


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


Modified: trunk/dynamic-docs/glossary/innodb.xml
===================================================================
--- trunk/dynamic-docs/glossary/innodb.xml	2011-01-12 15:51:59 UTC (rev 24781)
+++ trunk/dynamic-docs/glossary/innodb.xml	2011-01-12 16:05:14 UTC (rev 24782)
Changed blocks: 580, Lines Added: 33, Lines Deleted: 1186; 111187 bytes

@@ -5,7 +5,6 @@
   <glossent id="acid">
 
     <gterm>ACID</gterm>
-
     <def>
 
       <para>

@@ -15,7 +14,6 @@
         <emphasis role="bold">transaction</emphasis>. The transactional
         features of InnoDB adhere to the ACID principles.
       </para>
-
       <para>
         Transactions are atomic units of work that can be committed or
         rolled back. When a transaction makes multiple changes to the

@@ -23,12 +21,10 @@
         committed, or all the changes are undone when the transaction is
         rolled back.
       </para>
-
       <para>
         The database remains in a consistent state at all times -- after
         each commit or rollback, and while transactions are in progress.
       </para>
-
       <para>
         Transactions are protected (isolated) from each other while they
         are in progress; they cannot interfere with each other or see

@@ -39,7 +35,6 @@
         increased performance, when they can be sure that the
         transactions really do not interfere with each other.)
       </para>
-
       <para>
         The results of transactions are durable: once a commit operation
         succeeds, the changes made by that transaction are safe from

@@ -53,17 +48,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="rollback" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="doublewrite_buffer" />
 
   </glossent>

@@ -71,7 +60,6 @@
   <glossent id="adaptive_flushing">
 
     <gterm>adaptive flushing</gterm>
-
     <def>
 
       <para>

@@ -89,15 +77,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="flush" />
-
     <gseealso glosid="plugin" />
-
     <gseealso glosid="checkpoint" />
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="data_files" />
 
   </glossent>

@@ -105,7 +88,6 @@
   <glossent id="adaptive_hash_index">
 
     <gterm>adaptive hash index</gterm>
-
     <def>
 
       <para>

@@ -115,7 +97,6 @@
         defined for a table. If InnoDB notices that queries could
         benefit from a hash index, it builds one automatically.
       </para>
-
       <para>
         The hash index is always built based on an existing
         <emphasis role="bold">B-tree</emphasis> index on the table.

@@ -126,7 +107,6 @@
         the buffer pool. InnoDB builds hash indexes on demand for those
         pages of the index that are often accessed.
       </para>
-
       <para>
         In a sense, the adaptive hash index configures InnoDB at runtime
         to take advantage of ample main memory, coming closer to the

@@ -134,7 +114,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="b_tree" />
 
   </glossent>

@@ -142,7 +121,6 @@
   <glossent id="aio" class="acronym">
 
     <gterm>AIO</gterm>
-
     <def>
 
       <para>

@@ -151,7 +129,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="asynchronous_io" />
 
   </glossent>

@@ -159,7 +136,6 @@
   <glossent id="antelope">
 
     <gterm>Antelope</gterm>
-
     <def>
 
       <para>

@@ -172,30 +148,20 @@
         available in the <emphasis role="bold">Barracuda</emphasis> file
         format.
       </para>
-
       <para>
         You can select the file format to use through the
         <literal>innodb_file_format</literal> option.
       </para>
 
     </def>
-
     <gseealso glosid="barracuda" />
-
     <gseealso glosid="file_format" />
-
     <gseealso glosid="ibdata_file" />
-
     <gseealso glosid="redundant_row_format" />
-
     <gseealso glosid="compact_row_format" />
-
     <gseealso glosid="dynamic_row_format" />
-
     <gseealso glosid="compressed_row_format" />
-
     <gseealso glosid="row_format" />
-
     <gseealso glosid="innodb_file_format" />
 
   </glossent>

@@ -203,7 +169,6 @@
   <glossent id="application_programming_interface">
 
     <gterm>application programming interface (API)</gterm>
-
     <def>
 
       <para>

@@ -219,7 +184,6 @@
   <glossent id="apply">
 
     <gterm>apply</gterm>
-
     <def>
 
       <para>

@@ -232,7 +196,6 @@
         <literal>ibbackup</literal> or <literal>innobackup</literal>
         commands.
       </para>
-
       <para>
         Before the changes are applied, we refer to the files as a
         <emphasis role="bold">raw backup</emphasis>. After the changes

@@ -244,15 +207,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="raw_backup" />
-
     <gseealso glosid="prepared_backup" />
-
     <gseealso glosid="ibbackup_logfile" />
 
   </glossent>

@@ -260,7 +218,6 @@
   <glossent id="arm_file">
 
     <gterm>.ARM file</gterm>
-
     <def>
 
       <para>

@@ -272,11 +229,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
-
     <gseealso glosid="arz_file" />
 
   </glossent>

@@ -284,7 +238,6 @@
   <glossent id="arz_file">
 
     <gterm>.ARZ file</gterm>
-
     <def>
 
       <para>

@@ -296,11 +249,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
-
     <gseealso glosid="arm_file" />
 
   </glossent>

@@ -308,7 +258,6 @@
   <glossent id="asynchronous_io">
 
     <gterm>asynchronous I/O</gterm>
-
     <def>
 
       <para>

@@ -322,7 +271,6 @@
         pool</emphasis> that have not actually been requested, but might
         be needed soon.
       </para>
-
       <para>
         Historically, InnoDB has used asynchronous I/O on Windows
         systems only. Starting with the InnoDB Plugin 1.1, InnoDB uses

@@ -332,9 +280,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="non_blocking_io" />
-
     <gseealso glosid="buffer_pool" />
 
   </glossent>

@@ -342,7 +288,6 @@
   <glossent id="auto_increment">
 
     <gterm>auto-increment</gterm>
-
     <def>
 
       <para>

@@ -352,7 +297,6 @@
         supports auto-increment only for <emphasis role="bold">primary
         key</emphasis> columns.
       </para>
-
       <para>
         It saves work for the developer, not to have to produce new
         unique values when inserting new rows. It provides useful

@@ -363,7 +307,6 @@
         change them; for this reason, primary key columns are often
         specified as auto-incrementing.
       </para>
-
       <para>
         Auto-increment columns can be problematic with statement-based
         replication, because replaying the statements on a slave might

@@ -382,19 +325,12 @@
       </para>
 
     </def>
-
     <gseealso glosid="primary_key" />
-
     <gseealso glosid="auto_increment_locking" />
-
     <gseealso glosid="statement_based_replication" />
-
     <gseealso glosid="row_based_replication" />
-
     <gseealso glosid="innodb_autoinc_lock_mode" />
-
     <gseealso glosid="row_based_replication" />
-
     <gseealso glosid="statement_based_replication" />
 
   </glossent>

@@ -402,7 +338,6 @@
   <glossent id="auto_increment_locking">
 
     <gterm>auto-increment locking</gterm>
-
     <def>
 
       <para>

@@ -421,11 +356,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="auto_increment" />
-
     <gseealso glosid="concurrency" />
-
     <gseealso glosid="innodb_autoinc_lock_mode" />
 
   </glossent>

@@ -433,7 +365,6 @@
   <glossent id="autocommit">
 
     <gterm>autocommit</gterm>
-
     <def>
 
       <para>

@@ -450,15 +381,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="sql" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="undo" />
 
   </glossent>

@@ -466,7 +392,6 @@
   <glossent id="b_tree">
 
     <gterm>B-tree</gterm>
-
     <def>
 
       <para>

@@ -477,12 +402,10 @@
         operators). This type of index is available for most storage
         engines, such as InnoDB and MyISAM.
       </para>
-
       <para>
         Because B-tree nodes can have many children, a B-tree is not the
         same as a binary tree, which is limited to 2 children per node.
       </para>
-
       <para>
         Contrast with <emphasis role="bold">hash index</emphasis>, which
         is only available in the MEMORY storage engine. The MEMORY

@@ -492,7 +415,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="hash_index" />
 
   </glossent>

@@ -500,7 +422,6 @@
   <glossent id="backticks">
 
     <gterm>backticks</gterm>
-
     <def>
 
       <para>

@@ -514,7 +435,6 @@
         used extensively in program-generated SQL statements, where the
         identifier names might not be known in advance.
       </para>
-
       <para>
         Many other database systems use double quotation marks
         (<literal>"</literal>) around such special names. For

@@ -524,7 +444,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="sql" />
 
   </glossent>

@@ -532,7 +451,6 @@
   <glossent id="barracuda">
 
     <gterm>Barracuda</gterm>
-
     <def>
 
       <para>

@@ -544,7 +462,6 @@
         select it through the <literal>innodb_file_format</literal>
         option.
       </para>
-
       <para>
         The <emphasis role="bold">MySQL Enterprise Backup</emphasis>
         product version 3.5 and above supports backing up tablespaces

@@ -552,21 +469,13 @@
       </para>
 
     </def>
-
     <gseealso glosid="antelope" />
-
     <gseealso glosid="file_format" />
-
     <gseealso glosid="ibdata_file" />
-
     <gseealso glosid="row_format" />
-
     <gseealso glosid="compact_row_format" />
-
     <gseealso glosid="compressed_row_format" />
-
     <gseealso glosid="dynamic_row_format" />
-
     <gseealso glosid="innodb_file_format" />
 
   </glossent>

@@ -574,7 +483,6 @@
   <glossent id="beta">
 
     <gterm>beta</gterm>
-
     <def>
 
       <para>

@@ -588,9 +496,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="early_adopter" />
-
     <gseealso glosid="ga" />
 
   </glossent>

@@ -598,7 +504,6 @@
   <glossent id="bottleneck">
 
     <gterm>bottleneck</gterm>
-
     <def>
 
       <para>

@@ -611,9 +516,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="concurrency" />
-
     <gseealso glosid="buffer_pool" />
 
   </glossent>

@@ -621,7 +524,6 @@
   <glossent id="buffer">
 
     <gterm>buffer</gterm>
-
     <def>
 
       <para>

@@ -638,11 +540,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="doublewrite_buffer" />
-
     <gseealso glosid="insert_buffer" />
 
   </glossent>

@@ -650,7 +549,6 @@
   <glossent id="buffer_pool">
 
     <gterm>buffer pool</gterm>
-
     <def>
 
       <para>

@@ -667,9 +565,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="page" />
-
     <gseealso glosid="lru" />
 
   </glossent>

@@ -677,7 +573,6 @@
   <glossent id="binary_log">
 
     <gterm>binary log</gterm>
-
     <def>
 
       <para>

@@ -689,13 +584,11 @@
         recommend always enabling it if you use replication or perform
         backups.
       </para>
-
       <para>
         You can examine the contents of the binary log, or replay those
         statements during replication or recovery, by using the
         <literal>mysqlbinlog</literal> command.
       </para>
-
       <para>
         For the <emphasis role="bold">MySQL Enterprise Backup</emphasis>
         product, the file name of the binary log and the current

@@ -704,7 +597,6 @@
         replication context, you can specify the
         <literal>--slave-info</literal> option.
       </para>
-
       <para>
         Prior to MySQL 5.0, a similar capability was available, known as
         the update log. In MySQL 5.0 and higher, the binary log replaces

@@ -712,7 +604,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="binlog" />
 
   </glossent>

@@ -720,7 +611,6 @@
   <glossent id="binlog">
 
     <gterm>binlog</gterm>
-
     <def>
 
       <para>

@@ -730,7 +620,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="binary_log" />
 
   </glossent>

@@ -738,7 +627,6 @@
   <glossent id="built_in">
 
     <gterm>built-in</gterm>
-
     <def>
 
       <para>

@@ -751,7 +639,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="plugin" />
 
   </glossent>

@@ -759,7 +646,6 @@
   <glossent id="business_rules">
 
     <gterm>business rules</gterm>
-
     <def>
 
       <para>

@@ -771,7 +657,6 @@
         through application logic, accurately reflect the real policies
         of the company and can handle real-life situations.
       </para>
-
       <para>
         For example, an employee leaving a company might trigger a
         sequence of actions from the human resources department. The

@@ -790,9 +675,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="relational" />
-
     <gseealso glosid="trigger" />
 
   </glossent>

@@ -800,7 +683,6 @@
   <glossent id="cache">
 
     <gterm>cache</gterm>
-
     <def>
 
       <para>

@@ -811,9 +693,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="buffer" />
 
   </glossent>

@@ -821,7 +701,6 @@
   <glossent id="cardinality">
 
     <gterm>cardinality</gterm>
-
     <def>
 
       <para>

@@ -833,7 +712,6 @@
         cardinality might not be a good way to determine the best query
         plan. (http://bugs.mysql.com/bug.php?id=36513)
       </para>
-
       <para>
         Cardinality can also apply to the number of distinct values
         present in multiple columns, as in a

@@ -841,13 +719,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="random_dive" />
-
     <gseealso glosid="index" />
-
     <gseealso glosid="composite_index" />
-
     <gseealso glosid="selectivity" />
 
   </glossent>

@@ -855,7 +729,6 @@
   <glossent id="change_buffering">
 
     <gterm>change buffering</gterm>
-
     <def>
 
       <para>

@@ -873,13 +746,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="insert_buffer" />
-
     <gseealso glosid="insert_buffering" />
-
     <gseealso glosid="delete_buffering" />
-
     <gseealso glosid="purge_buffering" />
 
   </glossent>

@@ -887,7 +756,6 @@
   <glossent id="checkpoint">
 
     <gterm>checkpoint</gterm>
-
     <def>
 
       <para>

@@ -902,13 +770,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="flush" />
-
     <gseealso glosid="lsn" />
-
     <gseealso glosid="data_files" />
 
   </glossent>

@@ -916,7 +780,6 @@
   <glossent id="child_table">
 
     <gterm>child table</gterm>
-
     <def>
 
       <para>

@@ -932,9 +795,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="foreign_key" />
-
     <gseealso glosid="parent_table" />
 
   </glossent>

@@ -942,7 +803,6 @@
   <glossent id="client">
 
     <gterm>client</gterm>
-
     <def>
 
       <para>

@@ -954,9 +814,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="server" />
-
     <gseealso glosid="mysql" />
 
   </glossent>

@@ -964,7 +822,6 @@
   <glossent id="clustered_index">
 
     <gterm>clustered index</gterm>
-
     <def>
 
       <para>

@@ -977,18 +834,14 @@
         the clustered index is an expensive operation, choose primary
         columns that are rarely or never updated.
       </para>
-
       <para>
         In the Oracle Database product, this type of table is known as
         an <emphasis role="bold">index-organized table</emphasis>.
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="primary_key" />
-
     <gseealso glosid="secondary_index" />
 
   </glossent>

@@ -996,7 +849,6 @@
   <glossent id="cold_backup">
 
     <gterm>cold backup</gterm>
-
     <def>
 
       <para>

@@ -1008,11 +860,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="backup" />
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="warm_backup" />
 
   </glossent>

@@ -1020,7 +869,6 @@
   <glossent id="column_index">
 
     <gterm>column index</gterm>
-
     <def>
 
       <para>

@@ -1028,9 +876,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="composite_index" />
 
   </glossent>

@@ -1038,7 +884,6 @@
   <glossent id="column_prefix">
 
     <gterm>column prefix</gterm>
-
     <def>
 
       <para>

@@ -1051,7 +896,6 @@
         making rows with different values appear to the query optimizer
         to be duplicates.)
       </para>
-
       <para>
         For columns containing binary values or long text strings, where
         sorting is not a major consideration and storing the entire

@@ -1061,7 +905,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
 
   </glossent>

@@ -1069,7 +912,6 @@
   <glossent id="commit">
 
     <gterm>commit</gterm>
-
     <def>
 
       <para>

@@ -1079,7 +921,6 @@
         <emphasis role="bold">rollback</emphasis>, which undoes any
         changes made in the transaction.
       </para>
-
       <para>
         InnoDB uses an <emphasis role="bold">optimistic</emphasis>
         mechanism for commits, so that changes can be written to the

@@ -1087,7 +928,6 @@
         makes the commit itself faster, with the tradeoff that more work
         is required in case of a rollback.
       </para>
-
       <para>
         By default, MySQL uses the
         <emphasis role="bold">autocommit</emphasis> setting, which

@@ -1095,15 +935,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="rollback" />
-
     <gseealso glosid="sql" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="optimistic" />
-
     <gseealso glosid="autocommit" />
 
   </glossent>

@@ -1111,7 +946,6 @@
   <glossent id="compact_row_format">
 
     <gterm>compact row format</gterm>
-
     <def>
 
       <para>

@@ -1120,7 +954,6 @@
         nulls and variable-length fields than the prior default
         (<emphasis role="bold">redundant row format</emphasis>).
       </para>
-
       <para>
         Because of the <emphasis role="bold">B-tree</emphasis> indexes
         that make row lookups so fast in InnoDB, there is little if any

@@ -1128,9 +961,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="row_format" />
-
     <gseealso glosid="redundant_row_format" />
 
   </glossent>

@@ -1138,7 +969,6 @@
   <glossent id="composite_index">
 
     <gterm>composite index</gterm>
-
     <def>
 
       <para>

@@ -1147,9 +977,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="index_prefix" />
 
   </glossent>

@@ -1157,7 +985,6 @@
   <glossent id="compressed_backup">
 
     <gterm>compressed backup</gterm>
-
     <def>
 
       <para>

@@ -1167,7 +994,6 @@
         compressed files are renamed with a <literal>.ibz</literal> file
         extension.
       </para>
-
       <para>
         Applying <emphasis role="bold">compression</emphasis> right at
         the start of the backup process helps to avoid storage overhead

@@ -1179,17 +1005,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="compression" />
-
     <gseealso glosid="tablespace" />
-
     <gseealso glosid="apply" />
-
     <gseealso glosid="binary_log" />
 
   </glossent>

@@ -1197,7 +1017,6 @@
   <glossent id="compression">
 
     <gterm>compression</gterm>
-
     <def>
 
       <para>

@@ -1209,7 +1028,6 @@
         with the <emphasis role="bold">MySQL Enterprise
         Backup</emphasis> product.
       </para>
-
       <para>
         When InnoDB table data is compressed, the compression applies to
         the <emphasis role="bold">table</emphasis> itself, any

@@ -1218,7 +1036,6 @@
         pool</emphasis>. Compression does not apply to pages in the
         <emphasis role="bold">undo buffer</emphasis>.
       </para>
-
       <para>
         The table compression feature requires using MySQL 5.5 or
         higher, or the InnoDB Plugin in MySQL 5.1 or earlier, and

@@ -1228,7 +1045,6 @@
         <emphasis role="bold">innodb_file_per_table</emphasis> setting
         turned on.
       </para>
-
       <para>
         The compression feature of the <emphasis role="bold">MySQL
         Enterprise Backup</emphasis> product makes a compressed copy of

@@ -1244,21 +1060,13 @@
       </para>
 
     </def>
-
     <gseealso glosid="table" />
-
     <gseealso glosid="index" />
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="undo_buffer" />
-
     <gseealso glosid="plugin" />
-
     <gseealso glosid="barracuda" />
-
     <gseealso glosid="compressed_row_format" />
-
     <gseealso glosid="hot_backup" />
 
   </glossent>

@@ -1266,7 +1074,6 @@
   <glossent id="compressed_row_format">
 
     <gterm>compressed row format</gterm>
-
     <def>
 
       <para>

@@ -1282,11 +1089,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="row_format" />
-
     <gseealso glosid="dynamic_row_format" />
-
     <gseealso glosid="barracuda" />
 
   </glossent>

@@ -1294,7 +1098,6 @@
   <glossent id="concatenated_index">
 
     <gterm>concatenated index</gterm>
-
     <gsee glosid="composite_index" />
 
   </glossent>

@@ -1302,7 +1105,6 @@
   <glossent id="concurrency">
 
     <gterm>concurrency</gterm>
-
     <def>
 
       <para>

@@ -1316,11 +1118,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="locking" />
 
   </glossent>

@@ -1328,7 +1127,6 @@
   <glossent id="configuration_file">
 
     <gterm>configuration file</gterm>
-
     <def>
 
       <para>

@@ -1339,7 +1137,6 @@
         number of options related to InnoDB under the
         <literal>[mysqld]</literal> section of the file.
       </para>
-
       <para>
         When you use the <emphasis role="bold">MySQL Enterprise
         Backup</emphasis> product, you typically use two configuration

@@ -1356,9 +1153,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="option_file" />
-
     <gseealso glosid="my_cnf" />
 
   </glossent>

@@ -1366,7 +1161,6 @@
   <glossent id="consistent_read">
 
     <gterm>consistent read</gterm>
-
     <def>
 
       <para>

@@ -1380,7 +1174,6 @@
         can reduce <emphasis role="bold">concurrency</emphasis> by
         forcing transactions to wait for other transactions to finish.
       </para>
-
       <para>
         With the <emphasis role="bold">repeatable read</emphasis>
         isolation level, the snapshot is based on the time when the

@@ -1389,7 +1182,6 @@
         the snapshot is reset to the time of each consistent read
         operation.
       </para>
-
       <para>
         Consistent read is the default mode in which InnoDB processes
         <literal>SELECT</literal> statements in

@@ -1401,27 +1193,16 @@
       </para>
 
     </def>
-
     <gseealso glosid="undo_log" />
-
     <gseealso glosid="concurrency" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="mvcc" />
-
     <gseealso glosid="repeatable_read" />
-
     <gseealso glosid="read_committed" />
-
     <gseealso glosid="read_uncommitted" />
-
     <gseealso glosid="serializable_read" />
 
   </glossent>

@@ -1429,7 +1210,6 @@
   <glossent id="constraint">
 
     <gterm>constraint</gterm>
-
     <def>
 
       <para>

@@ -1444,13 +1224,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="relational" />
-
     <gseealso glosid="foreign_key" />
-
     <gseealso glosid="unique_constraint" />
 
   </glossent>

@@ -1458,7 +1234,6 @@
   <glossent id="covering_index">
 
     <gterm>covering index</gterm>
-
     <def>
 
       <para>

@@ -1472,7 +1247,6 @@
         cannot apply this technique for queries against tables modified
         by a transactions, until that transaction ends.
       </para>
-
       <para>
         Any <emphasis role="bold">column index</emphasis> or
         <emphasis role="bold">composite index</emphasis> could act as a

@@ -1482,13 +1256,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="column_index" />
-
     <gseealso glosid="composite_index" />
-
     <gseealso glosid="secondary_index" />
 
   </glossent>

@@ -1496,7 +1266,6 @@
   <glossent id="crash_recovery">
 
     <gterm>crash recovery</gterm>
-
     <def>
 
       <para>

@@ -1508,7 +1277,6 @@
         is performed during shutdown by the
         <emphasis role="bold">purge</emphasis> operation.
       </para>
-
       <para>
         During normal operation, committed data can be stored in the
         insert buffer for a period of time before being written to the

@@ -1519,11 +1287,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="purge" />
-
     <gseealso glosid="doublewrite_buffer" />
-
     <gseealso glosid="insert_buffer" />
 
   </glossent>

@@ -1531,7 +1296,6 @@
   <glossent id="cursor">
 
     <gterm>cursor</gterm>
-
     <def>
 
       <para>

@@ -1541,7 +1305,6 @@
         in other high-level languages, producing each value from the
         result set as requested.
       </para>
-
       <para>
         Although usually SQL handles the processing of cursors for you,
         you might delve into the inner workings when dealing with

@@ -1549,7 +1312,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="query" />
 
   </glossent>

@@ -1557,7 +1319,6 @@
   <glossent id="data_definition_language">
 
     <gterm>data definition language</gterm>
-
     <gsee glosid="ddl" />
 
   </glossent>

@@ -1565,7 +1326,6 @@
   <glossent id="data_dictionary">
 
     <gterm>data dictionary</gterm>
-
     <def>
 
       <para>

@@ -1574,7 +1334,6 @@
         and table columns. These tables are part of the InnoDB
         <emphasis role="bold">system tablespace</emphasis>.
       </para>
-
       <para>
         Because the <emphasis role="bold">MySQL Enterprise
         Backup</emphasis> product always backs up the system tablespace,

@@ -1582,9 +1341,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="hot_backup" />
 
   </glossent>

@@ -1592,7 +1349,6 @@
   <glossent id="data_manipulation_language">
 
     <gterm>data manipulation language</gterm>
-
     <gsee glosid="dml" />
 
   </glossent>

@@ -1600,7 +1356,6 @@
   <glossent id="data_warehouse">
 
     <gterm>data warehouse</gterm>
-
     <def>
 
       <para>

@@ -1612,9 +1367,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="query" />
-
     <gseealso glosid="oltp" />
 
   </glossent>

@@ -1622,7 +1375,6 @@
   <glossent id="ddl">
 
     <gterm>DDL</gterm>
-
     <def>
 
       <para>

@@ -1636,7 +1388,6 @@
         FROM <replaceable>table_name</replaceable></literal> statement,
         even though the ultimate effect is similar.
       </para>
-
       <para>
         DDL statements automatically
         <emphasis role="bold">commit</emphasis> the current

@@ -1645,13 +1396,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="sql" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="rollback" />
 
   </glossent>

@@ -1659,7 +1406,6 @@
   <glossent id="dirty_page">
 
     <gterm>dirty page</gterm>
-
     <def>
 
       <para>

@@ -1670,13 +1416,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="page" />
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="flush" />
-
     <gseealso glosid="write_combining" />
 
   </glossent>

@@ -1684,7 +1426,6 @@
   <glossent id="dirty_read">
 
     <gterm>dirty read</gterm>
-
     <def>
 
       <para>

@@ -1694,7 +1435,6 @@
         with the <emphasis role="bold">isolation level</emphasis> known
         as <emphasis role="bold">read uncommitted</emphasis>.
       </para>
-
       <para>
         This kind of operation does not adhere to the
         <emphasis role="bold">ACID</emphasis> principle of database

@@ -1703,7 +1443,6 @@
         before being committed; then, the transaction doing the dirty
         read would be using data that was never confirmed as accurate.
       </para>
-
       <para>
         Its polar opposite is <emphasis role="bold">consistent
         read</emphasis>, where InnoDB goes to great lengths to ensure

@@ -1713,19 +1452,12 @@
       </para>
 
     </def>
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="rollback" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="read_uncommitted" />
-
     <gseealso glosid="read_committed" />
 
   </glossent>

@@ -1733,7 +1465,6 @@
   <glossent id="dml">
 
     <gterm>DML</gterm>
-
     <def>
 
       <para>

@@ -1747,7 +1478,6 @@
         <literal>INSERT</literal>, <literal>UPDATE</literal>, and
         <literal>DELETE</literal>.
       </para>
-
       <para>
         DML statements operate in the context of a
         <emphasis role="bold">transaction</emphasis>, so their effects

@@ -1756,15 +1486,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="sql" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="rollback" />
 
   </glossent>

@@ -1772,7 +1497,6 @@
   <glossent id="dynamic_row_format">
 
     <gterm>dynamic row format</gterm>
-
     <def>
 
       <para>

@@ -1786,9 +1510,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="row_format" />
-
     <gseealso glosid="barracuda" />
 
   </glossent>

@@ -1796,7 +1518,6 @@
   <glossent id="delete">
 
     <gterm>delete</gterm>
-
     <def>
 
       <para>

@@ -1809,7 +1530,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="purge" />
 
   </glossent>

@@ -1817,7 +1537,6 @@
   <glossent id="delete_buffering">
 
     <gterm>delete buffering</gterm>
-
     <def>
 
       <para>

@@ -1834,13 +1553,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="change_buffering" />
-
     <gseealso glosid="insert_buffer" />
-
     <gseealso glosid="insert_buffering" />
-
     <gseealso glosid="purge_buffering" />
 
   </glossent>

@@ -1848,13 +1563,11 @@
   <glossent id="descending_index">
 
     <gterm>descending index</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="index" />
 
   </glossent>

@@ -1862,7 +1575,6 @@
   <glossent id="doublewrite_buffer">
 
     <gterm>doublewrite buffer</gterm>
-
     <def>
 
       <para>

@@ -1876,7 +1588,6 @@
         find a good copy of the page from the doublewrite buffer during
         <emphasis role="bold">crash recovery</emphasis>.
       </para>
-
       <para>
         Although data is always written twice, the doublewrite buffer
         does not require twice as much I/O overhead or twice as many I/O

@@ -1884,16 +1595,13 @@
         sequential chunk, with a single <literal>fsync</literal> call to
         the operating system.
       </para>
-
       <para>
         The doublewrite buffer can be turned off by specifying the
         option <literal>innodb_doublewrite=0</literal>.
       </para>
 
     </def>
-
     <gseealso glosid="crash_recovery" />
-
     <gseealso glosid="purge" />
 
   </glossent>

@@ -1901,7 +1609,6 @@
   <glossent id="disk_based">
 
     <gterm>disk-based</gterm>
-
     <def>
 
       <para>

@@ -1913,7 +1620,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="in_memory_database" />
 
   </glossent>

@@ -1921,7 +1627,6 @@
   <glossent id="data_files">
 
     <gterm>data files</gterm>
-
     <def>
 
       <para>

@@ -1938,13 +1643,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="tablespace" />
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="data_dictionary" />
-
     <gseealso glosid="file_per_table" />
 
   </glossent>

@@ -1952,14 +1653,12 @@
   <glossent id="database">
 
     <gterm>database</gterm>
-
     <def>
 
       <para>
         An InnoDB database is largely defined by its
         <emphasis role="bold">data files</emphasis>.
       </para>
-
       <para>
         For long-time MySQL users, a database is a familiar notion.
         Users coming from an Oracle background will find that the MySQL

@@ -1967,7 +1666,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="data_files" />
 
   </glossent>

@@ -1975,7 +1673,6 @@
   <glossent id="deadlock">
 
     <gterm>deadlock</gterm>
-
     <def>
 
       <para>

@@ -1986,7 +1683,6 @@
         Because both transactions are waiting for a resource to become
         available, neither will ever release the locks it holds.
       </para>
-
       <para>
         A deadlock can occur when the transactions acquire locks on
         multiple tables, but in the opposite order. A deadlock can also

@@ -1996,7 +1692,6 @@
         transaction acquiring some locks but not others due to a timing
         issue.
       </para>
-
       <para>
         To reduce the possibility of deadlocks, use transactions rather
         than <literal>LOCK TABLE</literal> statements; keep transactions

@@ -2012,7 +1707,6 @@
         isolation level changes the behavior of read operations, while
         deadlocks occur because of write operations.
       </para>
-
       <para>
         If a deadlock does occur, InnoDB detects the condition and
         <emphasis role="bold">rolls back</emphasis> one of the

@@ -2024,21 +1718,13 @@
       </para>
 
     </def>
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="gap" />
-
     <gseealso glosid="concurrency" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="rollback" />
-
     <gseealso glosid="victim" />
 
   </glossent>

@@ -2046,7 +1732,6 @@
   <glossent id="deadlock_detection">
 
     <gterm>deadlock detection</gterm>
-
     <def>
 
       <para>

@@ -2058,13 +1743,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="deadlock" />
-
     <gseealso glosid="rollback" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="victim" />
 
   </glossent>

@@ -2072,7 +1753,6 @@
   <glossent id="early_adopter">
 
     <gterm>early adopter</gterm>
-
     <def>
 
       <para>

@@ -2086,9 +1766,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="beta" />
-
     <gseealso glosid="ga" />
 
   </glossent>

@@ -2096,7 +1774,6 @@
   <glossent id="embedded_innodb">
 
     <gterm>Embedded InnoDB</gterm>
-
     <def>
 
       <para>

@@ -2110,7 +1787,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="cursor" />
 
   </glossent>

@@ -2118,7 +1794,6 @@
   <glossent id="explicit_row_lock">
 
     <gterm>explicit row lock</gterm>
-
     <def>
 
       <para></para>

@@ -2130,7 +1805,6 @@
   <glossent id="eviction">
 
     <gterm>eviction</gterm>
-
     <def>
 
       <para>

@@ -2140,7 +1814,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="lru" />
 
   </glossent>

@@ -2148,7 +1821,6 @@
   <glossent id="exclusive_lock">
 
     <gterm>exclusive lock</gterm>
-
     <def>
 
       <para>

@@ -2166,19 +1838,12 @@
       </para>
 
     </def>
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="concurrency" />
-
     <gseealso glosid="repeatable_read" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="shared_lock" />
 
   </glossent>

@@ -2186,7 +1851,6 @@
   <glossent id="fixed_row_format">
 
     <gterm>fixed row format</gterm>
-
     <def>
 
       <para>

@@ -2200,9 +1864,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="row_format" />
-
     <gseealso glosid="compact_row_format" />
 
   </glossent>

@@ -2210,7 +1872,6 @@
   <glossent id="flush">
 
     <gterm>flush</gterm>
-
     <def>
 
       <para>

@@ -2221,7 +1882,6 @@
         <emphasis role="bold">undo log</emphasis>, and the
         <emphasis role="bold">buffer pool</emphasis>.
       </para>
-
       <para>
         Flushing can happen because a memory area becomes full and the
         system needs to free some space, because a

@@ -2232,13 +1892,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="redo_log" />
-
     <gseealso glosid="undo_log" />
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="commit" />
 
   </glossent>

@@ -2246,7 +1902,6 @@
   <glossent id="flush_list">
 
     <gterm>flush list</gterm>
-
     <def>
 
       <para>

@@ -2261,13 +1916,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="page" />
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="mini_transaction" />
-
     <gseealso glosid="mutex" />
 
   </glossent>

@@ -2275,7 +1926,6 @@
   <glossent id="foreign_key">
 
     <gterm>foreign key</gterm>
-
     <def>
 
       <para>

@@ -2284,7 +1934,6 @@
         both the <emphasis role="bold">parent table</emphasis> and the
         <emphasis role="bold">child table</emphasis>.
       </para>
-
       <para>
         In addition to enabling fast lookup of related information,
         foreign keys help to enforce referential integrity, by

@@ -2300,7 +1949,6 @@
         <emphasis role="bold">null</emphasis>, or automatically delete
         the corresponding rows in the other table.
       </para>
-
       <para>
         One of the stages in designing a
         <emphasis role="bold">normalized</emphasis> database is to

@@ -2311,19 +1959,12 @@
       </para>
 
     </def>
-
     <gseealso glosid="parent_table" />
-
     <gseealso glosid="child_table" />
-
     <gseealso glosid="relational" />
-
     <gseealso glosid="foreign_key_constraint" />
-
     <gseealso glosid="null" />
-
     <gseealso glosid="normalized" />
-
     <gseealso glosid="join" />
 
   </glossent>

@@ -2331,7 +1972,6 @@
   <glossent id="foreign_key_constraint">
 
     <gterm>foreign key constraint</gterm>
-
     <def>
 
       <para>

@@ -2348,13 +1988,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="constraint" />
-
     <gseealso glosid="foreign_key" />
-
     <gseealso glosid="child_table" />
-
     <gseealso glosid="null" />
 
   </glossent>

@@ -2362,7 +1998,6 @@
   <glossent id="full_table_scan">
 
     <gterm>full table scan</gterm>
-
     <def>
 
       <para>

@@ -2375,7 +2010,6 @@
         have implications for the algorithms used in query optimization
         and managing the buffer pool.
       </para>
-
       <para>
         The purpose of <emphasis role="bold">indexes</emphasis> is to
         allow lookups for specific values or ranges of values within a

@@ -2383,11 +2017,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="lru" />
-
     <gseealso glosid="index" />
 
   </glossent>

@@ -2395,7 +2026,6 @@
   <glossent id="fast_index_creation">
 
     <gterm>fast index creation</gterm>
-
     <def>
 
       <para>

@@ -2404,7 +2034,6 @@
         completely rewrite the associated table. The speedup applies to
         dropping secondary indexes also.
       </para>
-
       <para>
         Because index maintenance can add performance overhead to many
         data transfer operations, consider doing operations such as

@@ -2412,7 +2041,6 @@
         <literal>INSERT INTO ... SELECT * FROM ...</literal> without any
         secondary indexes in place, and creating the indexes afterward.
       </para>
-
       <para>
         Even if you do not use the InnoDB Plugin as your primary storage
         engine, you can take advantage of this capability by enabling

@@ -2422,9 +2050,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="secondary_index" />
 
   </glossent>

@@ -2432,25 +2058,20 @@
   <glossent id="fast_shutdown">
 
     <gterm>fast shutdown</gterm>
-
     <def>
 
       <para>
         A shutdown procedure that is required before installation of the
         InnoDB Plugin. From the MySQL command line, issue the following
         command before performing the shutdown:
-
 <programlisting>SET GLOBAL innodb_fast_shutdown=0;</programlisting>
-
         To make this type of shutdown the default, specify by the
         configuration parameter
         <literal>innodb_fast_shutdown=0</literal>.
       </para>
 
     </def>
-
     <gseealso glosid="slow_shutdown" />
-
     <gseealso glosid="shutdown" />
 
   </glossent>

@@ -2458,14 +2079,12 @@
   <glossent id="frm_file">
 
     <gterm>.FRM file</gterm>
-
     <def>
 
       <para>
         The file containing the metadata, such as the table definition,
         of a MySQL table.
       </para>
-
       <para>
         For backups, you must always keep the full set of
         <literal>.FRM</literal> files along with the backup data, to be

@@ -2477,14 +2096,12 @@
         <emphasis role="bold">ibbackup </emphasis> command instead, you
         must copy the <literal>.FRM</literal> files yourself.
       </para>
-
       <para>
         Although each InnoDB table has a <literal>.FRM</literal> file,
         InnoDB maintains its own table metadata in the system
         tablespace; the <literal>.FRM</literal> files are not needed for
         InnoDB to operate on InnoDB tables.
       </para>
-
       <para>
         These files are backed up by the <emphasis role="bold">MySQL
         Enterprise Backup</emphasis> product. These files must not be

@@ -2499,11 +2116,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
-
     <gseealso glosid="ibbackup_command" />
 
   </glossent>

@@ -2511,7 +2125,6 @@
   <glossent id="file_format">
 
     <gterm>file format</gterm>
-
     <def>
 
       <para>

@@ -2521,13 +2134,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="antelope" />
-
     <gseealso glosid="barracuda" />
-
     <gseealso glosid="ibdata_file" />
-
     <gseealso glosid="row_format" />
 
   </glossent>

@@ -2535,7 +2144,6 @@
   <glossent id="file_per_table">
 
     <gterm>file-per-table</gterm>
-
     <def>
 
       <para>

@@ -2551,11 +2159,9 @@
         and the reclaimed space can be used by the operating system
         rather than remaining reserved for InnoDB.
       </para>
-
       <para>
         This mode is the default setting in MySQL 5.5.5 and higher.
       </para>
-
       <para>
         The <emphasis role="bold">MySQL Enterprise Backup</emphasis>
         product is more flexible for tables that are in their own files.

@@ -2566,15 +2172,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="ibdata_file" />
-
     <gseealso glosid="innodb_file_per_table" />
-
     <gseealso glosid="file_format" />
-
     <gseealso glosid="row_format" />
 
   </glossent>

@@ -2582,7 +2183,6 @@
   <glossent id="ga">
 
     <gterm>GA</gterm>
-
     <def>
 
       <para>

@@ -2592,9 +2192,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="beta" />
-
     <gseealso glosid="early_adopter" />
 
   </glossent>

@@ -2602,7 +2200,6 @@
   <glossent id="gap">
 
     <gterm>gap</gterm>
-
     <def>
 
       <para>

@@ -2615,7 +2212,6 @@
         prevents another transaction from inserting a new value that is
         greater than 10.
       </para>
-
       <para>
         Gap locks are part of the tradeoff between performance and
         <emphasis role="bold">concurrency</emphasis>, and are used in

@@ -2624,15 +2220,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="concurrency" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="supremum_record" />
-
     <gseealso glosid="infimum_record" />
 
   </glossent>

@@ -2640,7 +2231,6 @@
   <glossent id="group_commit">
 
     <gterm>group commit</gterm>
-
     <def>
 
       <para>

@@ -2650,7 +2240,6 @@
         <emphasis role="bold">commit</emphasis> operations, rather than
         flushing and syncing separately for each commit.
       </para>
-
       <para>
         When the binlog is enabled, you typically also set the
         configuration option <literal>sync_binlog=0</literal>, because

@@ -2659,13 +2248,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="plugin" />
-
     <gseealso glosid="xa" />
-
     <gseealso glosid="log_write" />
 
   </glossent>

@@ -2673,7 +2258,6 @@
   <glossent id="hash_index">
 
     <gterm>hash_index</gterm>
-
     <def>
 
       <para>

@@ -2685,7 +2269,6 @@
         for general-purpose queries, B-tree indexes are often a better
         choice.
       </para>
-
       <para>
         The InnoDB storage engine includes a variant of this index type,
         the <emphasis role="bold">adaptive hash index</emphasis>, that

@@ -2694,11 +2277,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="b_tree" />
-
     <gseealso glosid="adaptive_hash_index" />
 
   </glossent>

@@ -2706,7 +2286,6 @@
   <glossent id="heartbeat">
 
     <gterm>heartbeat</gterm>
-
     <def>
 
       <para>

@@ -2721,11 +2300,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="replication" />
-
     <gseealso glosid="master_database" />
-
     <gseealso glosid="slave_database" />
 
   </glossent>

@@ -2733,7 +2309,6 @@
   <glossent id="hot">
 
     <gterm>hot</gterm>
-
     <def>
 
       <para>

@@ -2742,7 +2317,6 @@
         locking or mutual exclusion, that it results in a performance or
         scalability issue.
       </para>
-
       <para>
         Although <quote>hot</quote> typically indicates an undesirable
         condition, a <emphasis role="bold">hot backup</emphasis> is the

@@ -2750,7 +2324,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="hot_backup" />
 
   </glossent>

@@ -2758,7 +2331,6 @@
   <glossent id="hot_backup">
 
     <gterm>hot backup</gterm>
-
     <def>
 
       <para>

@@ -2769,14 +2341,12 @@
         must exclude any data that was deleted while the backup was in
         process; and it must ignore any changes that were not committed.
       </para>
-
       <para>
         The Oracle product that performs hot backups, of InnoDB tables
         especially but also tables from MyISAM and other storage
         engines, is known as <emphasis role="bold">MySQL Enterprise
         Backup</emphasis>.
       </para>
-
       <para>
         The hot backup process consists of two stages. The initial
         copying of the data files produces a <emphasis role="bold">raw

@@ -2788,13 +2358,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="raw_backup" />
-
     <gseealso glosid="apply" />
-
     <gseealso glosid="prepared_backup" />
 
   </glossent>

@@ -2802,7 +2368,6 @@
   <glossent id="ibbackup_command">
 
     <gterm>ibbackup command</gterm>
-
     <def>
 
       <para>

@@ -2819,11 +2384,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="innobackup_command" />
 
   </glossent>

@@ -2831,7 +2393,6 @@
   <glossent id="ibbackup_logfile">
 
     <gterm>ibbackup_logfile</gterm>
-
     <def>
 
       <para>

@@ -2852,15 +2413,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="raw_backup" />
-
     <gseealso glosid="apply" />
-
     <gseealso glosid="prepared_backup" />
 
   </glossent>

@@ -2868,7 +2424,6 @@
   <glossent id="information_schema">
 
     <gterm>information schema</gterm>
-
     <def>
 
       <para>

@@ -2879,7 +2434,6 @@
         <literal>INFORMATION_SCHEMA.TABLES</literal> and
         <literal>INFORMATION_SCHEMA.COLUMNS</literal>.
       </para>
-
       <para>
         The InnoDB <emphasis role="bold">Plugin</emphasis> introduced
         some tables into the information schema that are specific to

@@ -2895,15 +2449,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="schema" />
-
     <gseealso glosid="data_dictionary" />
-
     <gseealso glosid="compression" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="locking" />
 
   </glossent>

@@ -2911,7 +2460,6 @@
   <glossent id="innobackup_command">
 
     <gterm>innobackup command</gterm>
-
     <def>
 
       <para>

@@ -2926,11 +2474,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="ibbackup_command" />
 
   </glossent>

@@ -2938,7 +2483,6 @@
   <glossent id="innodb_autoinc_lock_mode">
 
     <gterm>innodb_autoinc_lock_mode</gterm>
-
     <def>
 
       <para>

@@ -2963,7 +2507,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="auto_increment_locking" />
 
   </glossent>

@@ -2971,7 +2514,6 @@
   <glossent id="innodb_strict_mode">
 
     <gterm>innodb_strict_mode</gterm>
-
     <def>
 
       <para>

@@ -2980,13 +2522,11 @@
         that are normally treated as warnings, cause errors instead (and
         the underlying statements fail).
       </para>
-
       <para>
         This mode is the default setting in MySQL 5.5.5 and higher.
       </para>
 
     </def>
-
     <gseealso glosid="strict_mode" />
 
   </glossent>

@@ -2994,7 +2534,6 @@
   <glossent id="innodb_hot_backup">
 
     <gterm>InnoDB Hot Backup</gterm>
-
     <def>
 
       <para>

@@ -3003,7 +2542,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
 
   </glossent>

@@ -3011,7 +2549,6 @@
   <glossent id="ib_logfile">
 
     <gterm>ib_logfile</gterm>
-
     <def>
 
       <para>

@@ -3022,16 +2559,13 @@
         statements are replayed automatically to correct data written by
         incomplete transactions, on startup following a crash.
       </para>
-
       <para>
         This data can not be used for manual recovery; for that type of
         operation, use the <emphasis role="bold">binary log</emphasis>.
       </para>
 
     </def>
-
     <gseealso glosid="redo_log" />
-
     <gseealso glosid="binary_log" />
 
   </glossent>

@@ -3039,7 +2573,6 @@
   <glossent id="ib_file_set">
 
     <gterm>ib-file set</gterm>
-
     <def>
 
       <para>

@@ -3054,9 +2587,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="database" />
-
     <gseealso glosid="schema" />
 
   </glossent>

@@ -3064,7 +2595,6 @@
   <glossent id="infimum_record">
 
     <gterm>infimum record</gterm>
-
     <def>
 
       <para>

@@ -3078,11 +2608,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="gap" />
-
     <gseealso glosid="supremum_record" />
-
     <gseealso glosid="pseudo_record" />
 
   </glossent>

@@ -3090,7 +2617,6 @@
   <glossent id="ibd_file">
 
     <gterm>ibd file</gterm>
-
     <def>
 
       <para>

@@ -3104,13 +2630,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="tablespace" />
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="file_per_table" />
-
     <gseealso glosid="ibz_file" />
 
   </glossent>

@@ -3118,7 +2640,6 @@
   <glossent id="ibdata_file">
 
     <gterm>ibdata file</gterm>
-
     <def>
 
       <para>

@@ -3131,15 +2652,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="antelope" />
-
     <gseealso glosid="barracuda" />
-
     <gseealso glosid="file_format" />
-
     <gseealso glosid="file_per_table" />
-
     <gseealso glosid="system_tablespace" />
 
   </glossent>

@@ -3147,7 +2663,6 @@
   <glossent id="ibz_file">
 
     <gterm>ibz file</gterm>
-
     <def>
 
       <para>

@@ -3160,7 +2675,6 @@
         <literal>.ibd</literal> extension to a <literal>.ibz</literal>
         extension.
       </para>
-
       <para>
         The compression applied during backup is distinct from the
         <emphasis role="bold">compressed row format</emphasis> that

@@ -3172,17 +2686,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="tablespace" />
-
     <gseealso glosid="file_per_table" />
-
     <gseealso glosid="ibd_file" />
-
     <gseealso glosid="compressed_backup" />
-
     <gseealso glosid="compressed_row_format" />
 
   </glossent>

@@ -3190,7 +2698,6 @@
   <glossent id="in_memory_database">
 
     <gterm>in-memory database</gterm>
-
     <def>
 
       <para>

@@ -3206,9 +2713,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="disk_based" />
-
     <gseealso glosid="acid" />
 
   </glossent>

@@ -3216,7 +2721,6 @@
   <glossent id="innodb_file_per_table">
 
     <gterm>innodb_file_per_table</gterm>
-
     <def>
 
       <para>

@@ -3229,18 +2733,14 @@
         named tables in <emphasis role="bold">MySQL Enterprise
         Backup</emphasis>.
       </para>
-
       <para>
         This option was once static, but can now be set using the
         <literal>SET GLOBAL</literal> command.
       </para>
 
     </def>
-
     <gseealso glosid="data_files" />
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="file_per_table" />
 
   </glossent>

@@ -3248,7 +2748,6 @@
   <glossent id="innodb_file_format">
 
     <gterm>innodb_file_format</gterm>
-
     <def>
 
       <para>

@@ -3262,19 +2761,12 @@
       </para>
 
     </def>
-
     <gseealso glosid="file_format" />
-
     <gseealso glosid="tablespace" />
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="antelope" />
-
     <gseealso glosid="barracuda" />
-
     <gseealso glosid="file_per_table" />
-
     <gseealso glosid="innodb_file_per_table" />
 
   </glossent>

@@ -3282,7 +2774,6 @@
   <glossent id="innodb_lock_wait_timeout">
 
     <gterm>innodb_lock_wait_timeout</gterm>
-
     <def>
 
       <para>

@@ -3294,11 +2785,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="victim" />
-
     <gseealso glosid="deadlock" />
-
     <gseealso glosid="deadlock_detection" />
 
   </glossent>

@@ -3306,13 +2794,11 @@
   <glossent id="innodb_table_locks">
 
     <gterm>innodb_table_locks</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="locking" />
 
   </glossent>

@@ -3320,13 +2806,11 @@
   <glossent id="innodb_locks_unsafe_for_binlog">
 
     <gterm>innodb_locks_unsafe_for_binlog</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="locking" />
 
   </glossent>

@@ -3334,13 +2818,11 @@
   <glossent id="implicit_row_lock">
 
     <gterm>implicit row lock</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="locking" />
 
   </glossent>

@@ -3348,7 +2830,6 @@
   <glossent id="incremental_backup">
 
     <gterm>incremental backup</gterm>
-
     <def>
 
       <para>

@@ -3363,7 +2844,6 @@
         backup up-to-date by applying each incremental backup to it,
         then perform a single restore operation.
       </para>
-
       <para>
         The granularity of changed data is at the
         <emphasis role="bold">page</emphasis> level. A page might

@@ -3372,11 +2852,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="page" />
 
   </glossent>

@@ -3384,7 +2861,6 @@
   <glossent id="index">
 
     <gterm>index</gterm>
-
     <def>
 
       <para>

@@ -3394,21 +2870,13 @@
       </para>
 
     </def>
-
     <gseealso glosid="clustered_index" />
-
     <gseealso glosid="primary_key" />
-
     <gseealso glosid="secondary_index" />
-
     <gseealso glosid="b_tree" />
-
     <gseealso glosid="column_index" />
-
     <gseealso glosid="composite_index" />
-
     <gseealso glosid="covering_index" />
-
     <gseealso glosid="partial_index" />
 
   </glossent>

@@ -3416,7 +2884,6 @@
   <glossent id="index_prefix">
 
     <gterm>index prefix</gterm>
-
     <def>
 
       <para>

@@ -3429,9 +2896,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="composite_index" />
 
   </glossent>

@@ -3439,7 +2904,6 @@
   <glossent id="innodb">
 
     <gterm>InnoDB</gterm>
-
     <def>
 
       <para>

@@ -3452,13 +2916,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="storage_engine" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="hot_backup" />
 
   </glossent>

@@ -3466,7 +2926,6 @@
   <glossent id="insert">
 
     <gterm>insert</gterm>
-
     <def>
 
       <para>

@@ -3485,15 +2944,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="sql" />
-
     <gseealso glosid="dml" />
-
     <gseealso glosid="insert_buffer" />
-
     <gseealso glosid="change_buffering" />
-
     <gseealso glosid="auto_increment" />
 
   </glossent>

@@ -3501,7 +2955,6 @@
   <glossent id="insert_buffer">
 
     <gterm>insert buffer</gterm>
-
     <def>
 
       <para>

@@ -3516,7 +2969,6 @@
         buffering</emphasis>, and <emphasis role="bold">purge
         buffering</emphasis>.
       </para>
-
       <para>
         Changes are only recorded in the insert buffer when the relevant
         page from the secondary index is not in the

@@ -3532,7 +2984,6 @@
         more efficiently than if each value were written to disk
         immediately.
       </para>
-
       <para>
         Physically, the insert buffer is part of the
         <emphasis role="bold">system tablespace</emphasis>, so that the

@@ -3540,28 +2991,19 @@
         changes are only applied when the pages are brought into the
         buffer pool due to some other read operation.
       </para>
-
       <para>
         To see information about the current data in the insert buffer,
         issue the <literal>SHOW INNODB STATUS</literal> command.
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="page" />
-
     <gseealso glosid="purge" />
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="change_buffering" />
-
     <gseealso glosid="insert_buffering" />
-
     <gseealso glosid="delete_buffering" />
-
     <gseealso glosid="purge_buffering" />
 
   </glossent>

@@ -3569,7 +3011,6 @@
   <glossent id="insert_buffering">
 
     <gterm>insert buffering</gterm>
-
     <def>
 
       <para>

@@ -3582,7 +3023,6 @@
         are <emphasis role="bold">delete buffering</emphasis> and
         <emphasis role="bold">purge buffering</emphasis>.
       </para>
-
       <para>
         Insert buffering is not used if the secondary index is unique,
         because the uniqueness of new values cannot be verified before

@@ -3591,13 +3031,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="change_buffering" />
-
     <gseealso glosid="insert_buffer" />
-
     <gseealso glosid="delete_buffering" />
-
     <gseealso glosid="purge_buffering" />
 
   </glossent>

@@ -3605,19 +3041,14 @@
   <glossent id="insert_intention_gap_lock">
 
     <gterm>insert-intention gap lock</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="intention_lock" />
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="gap" />
 
   </glossent>

@@ -3625,9 +3056,7 @@
   <glossent id="intention_exclusive_lock">
 
     <gterm>intention exclusive lock</gterm>
-
     <gsee glosid="intention_lock" />
-
 <!--
 <def>
 <para>

@@ -3646,7 +3075,6 @@
   <glossent id="intention_lock">
 
     <gterm>intention lock</gterm>
-
     <def>
 
       <para>

@@ -3666,17 +3094,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="lock_mode" />
-
     <gseealso glosid="lock" />
-
 <!-- <gseealso glosid="intention_exclusive_lock" /> -->
-
 <!-- <gseealso glosid="intention_shared_lock" /> -->
-
     <gseealso glosid="insert_intention_gap_lock" />
 
   </glossent>

@@ -3684,9 +3106,7 @@
   <glossent id="intention_shared_lock">
 
     <gterm>intention shared lock</gterm>
-
     <gsee glosid="intention_lock" />
-
 <!--
 <def>
 <para>

@@ -3703,7 +3123,6 @@
   <glossent id="isolation_level">
 
     <gterm>isolation level</gterm>
-
     <def>
 
       <para>

@@ -3715,7 +3134,6 @@
         multiple <emphasis role="bold">transactions</emphasis> are
         making changes and performing queries at the same time.
       </para>
-
       <para>
         From highest amount of consistency and protection to the least,
         the isolation levels supported by InnoDB are:

@@ -3724,7 +3142,6 @@
         <emphasis role="bold">consistent read</emphasis>, and
         <emphasis role="bold">read uncommitted</emphasis>.
       </para>
-
       <para>
         With the built-in InnoDB storage engine and the InnoDB Plugin,
         many users can keep the default isolation level

@@ -3741,17 +3158,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="repeatable_read" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="serializable_read" />
-
     <gseealso glosid="read_uncommitted" />
 
   </glossent>

@@ -3759,7 +3170,6 @@
   <glossent id="join">
 
     <gterm>join</gterm>
-
     <def>
 
       <para>

@@ -3770,9 +3180,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="query" />
-
     <gseealso glosid="foreign_key" />
 
   </glossent>

@@ -3780,7 +3188,6 @@
   <glossent id="key_block_size">
 
     <gterm>key_block_size</gterm>
-
     <def>
 
       <para>

@@ -3792,7 +3199,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="compressed_row_format" />
 
   </glossent>

@@ -3800,7 +3206,6 @@
   <glossent id="logical_backup">
 
     <gterm>logical backup</gterm>
-
     <def>
 
       <para>

@@ -3814,9 +3219,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="backup" />
-
     <gseealso glosid="physical_backup" />
 
   </glossent>

@@ -3824,7 +3227,6 @@
   <glossent id="loose_">
 
     <gterm>loose_</gterm>
-
     <def>
 
       <para>

@@ -3846,7 +3248,6 @@
   <glossent id="list">
 
     <gterm>list</gterm>
-
     <def>
 
       <para>

@@ -3858,13 +3259,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="eviction" />
-
     <gseealso glosid="sublist" />
-
     <gseealso glosid="lru" />
 
   </glossent>

@@ -3872,7 +3269,6 @@
   <glossent id="lsn">
 
     <gterm>LSN</gterm>
-
     <def>
 
       <para>

@@ -3884,7 +3280,6 @@
         middle of one or more transactions.) It is used internally by
         InnoDB during crash recovery and for managing the buffer pool.
       </para>
-
       <para>
         In the <emphasis role="bold">MySQL Enterprise Backup</emphasis>
         product, you can specify an LSN to represent the point in time

@@ -3897,11 +3292,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="redo_log" />
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="incremental_backup" />
 
   </glossent>

@@ -3909,7 +3301,6 @@
   <glossent id="latch">
 
     <gterm>latch</gterm>
-
     <def>
 
       <para>

@@ -3928,17 +3319,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="mutex" />
-
     <gseealso glosid="rw_lock" />
-
     <gseealso glosid="data_dictionary" />
-
     <gseealso glosid="performance_schema" />
 
   </glossent>

@@ -3946,7 +3331,6 @@
   <glossent id="lock">
 
     <gterm>lock</gterm>
-
     <def>
 
       <para>

@@ -3960,15 +3344,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="lock_mode" />
-
     <gseealso glosid="mutex" />
-
     <gseealso glosid="latch" />
-
     <gseealso glosid="pthreads" />
 
   </glossent>

@@ -3976,7 +3355,6 @@
   <glossent id="lock_escalation">
 
     <gterm>lock escalation</gterm>
-
     <def>
 
       <para>

@@ -3988,11 +3366,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="row_lock" />
-
     <gseealso glosid="table_lock" />
 
   </glossent>

@@ -4000,7 +3375,6 @@
   <glossent id="locking">
 
     <gterm>locking</gterm>
-
     <def>
 
       <para>

@@ -4019,19 +3393,12 @@
       </para>
 
     </def>
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="mutex" />
-
     <gseealso glosid="latch" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="concurrency" />
 
   </glossent>

@@ -4039,7 +3406,6 @@
   <glossent id="lock_mode">
 
     <gterm>lock mode</gterm>
-
     <def>
 
       <para>

@@ -4047,13 +3413,11 @@
         transactions can acquire an S lock on that same row at the same
         time.
       </para>
-
       <para>
         An exclusive (X) lock allows a transaction to update or delete a
         row. No other transaction can acquire any kind of lock on that
         same row at the same time.
       </para>
-
       <para>
         <emphasis role="bold">Intention locks</emphasis> apply to the
         table level, and are used to indicate what kind of lock the

@@ -4070,11 +3434,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="intention_lock" />
 
   </glossent>

@@ -4082,17 +3443,13 @@
   <glossent id="lock_monitor">
 
     <gterm>lock monitor</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="deadlock" />
 
   </glossent>

@@ -4100,13 +3457,11 @@
   <glossent id="log_write">
 
     <gterm>log write</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="group_commit" />
 
   </glossent>

@@ -4114,7 +3469,6 @@
   <glossent id="lru">
 
     <gterm>LRU</gterm>
-
     <def>
 
       <para>

@@ -4132,9 +3486,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="eviction" />
 
   </glossent>

@@ -4142,7 +3494,6 @@
   <glossent id="master_database">
 
     <gterm>master database</gterm>
-
     <def>
 
       <para>

@@ -4154,9 +3505,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="replication" />
-
     <gseealso glosid="slave_database" />
 
   </glossent>

@@ -4164,13 +3513,11 @@
   <glossent id="master_thread">
 
     <gterm>master thread</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="thread" />
 
   </glossent>

@@ -4178,7 +3525,6 @@
   <glossent id="mrg_file">
 
     <gterm>.MRG file</gterm>
-
     <def>
 
       <para>

@@ -4190,9 +3536,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
 
   </glossent>

@@ -4200,7 +3544,6 @@
   <glossent id="multiversion_concurrency_control">
 
     <gterm>multiversion concurrency control</gterm>
-
     <gsee glosid="mvcc" />
 
   </glossent>

@@ -4208,7 +3551,6 @@
   <glossent id="mvcc">
 
     <gterm>MVCC</gterm>
-
     <def>
 
       <para>

@@ -4224,7 +3566,6 @@
         <emphasis role="bold">locks</emphasis> held by the other
         transactions.
       </para>
-
       <para>
         This technique is not universal in the database world. Some
         other database products, and some other storage engines within

@@ -4232,15 +3573,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="concurrency" />
-
     <gseealso glosid="lock" />
 
   </glossent>

@@ -4248,7 +3584,6 @@
   <glossent id="mid_point_insertion_strategy">
 
     <gterm>mid-point insertion strategy</gterm>
-
     <def>
 
       <para>

@@ -4262,11 +3597,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="lru" />
-
     <gseealso glosid="full_table_scan" />
 
   </glossent>

@@ -4274,7 +3606,6 @@
   <glossent id="mysql">
 
     <gterm>mysql</gterm>
-
     <def>
 
       <para>

@@ -4285,7 +3616,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysqld" />
 
   </glossent>

@@ -4293,7 +3623,6 @@
   <glossent id="mysql_enterprise_backup">
 
     <gterm>MySQL Enterprise Backup</gterm>
-
     <def>
 
       <para>

@@ -4305,9 +3634,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="innodb" />
 
   </glossent>

@@ -4315,7 +3642,6 @@
   <glossent id="mysqld">
 
     <gterm>mysqld</gterm>
-
     <def>
 
       <para>

@@ -4326,7 +3652,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql" />
 
   </glossent>

@@ -4334,13 +3659,11 @@
   <glossent id="mysqldump">
 
     <gterm>mysqldump</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="hot_backup" />
 
   </glossent>

@@ -4348,13 +3671,11 @@
   <glossent id="monitor">
 
     <gterm>monitor</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="lock_monitor" />
 
   </glossent>

@@ -4362,7 +3683,6 @@
   <glossent id="myd_files">
 
     <gterm>.MYD files</gterm>
-
     <def>
 
       <para>

@@ -4374,11 +3694,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="myi_files" />
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
 
   </glossent>

@@ -4386,7 +3703,6 @@
   <glossent id="myi_files">
 
     <gterm>.MYI files</gterm>
-
     <def>
 
       <para>

@@ -4398,11 +3714,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="myd_files" />
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
 
   </glossent>

@@ -4410,7 +3723,6 @@
   <glossent id="mini_transaction">
 
     <gterm>mini-transaction</gterm>
-
     <def>
 
       <para>

@@ -4423,11 +3735,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="data_dictionary" />
-
     <gseealso glosid="ddl" />
-
     <gseealso glosid="transaction" />
 
   </glossent>

@@ -4435,7 +3744,6 @@
   <glossent id="multi_core">
 
     <gterm>multi-core</gterm>
-
     <def>
 
       <para>

@@ -4450,7 +3758,6 @@
   <glossent id="my_cnf">
 
     <gterm>my.cnf</gterm>
-
     <def>
 
       <para>

@@ -4458,9 +3765,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="option_file" />
-
     <gseealso glosid="my_ini" />
 
   </glossent>

@@ -4468,7 +3773,6 @@
   <glossent id="my_ini">
 
     <gterm>my.ini</gterm>
-
     <def>
 
       <para>

@@ -4476,9 +3780,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="option_file" />
-
     <gseealso glosid="my_cnf" />
 
   </glossent>

@@ -4486,7 +3788,6 @@
   <glossent id="mutex">
 
     <gterm>mutex</gterm>
-
     <def>
 
       <para>

@@ -4503,15 +3804,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="pthreads" />
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="rw_lock" />
-
     <gseealso glosid="latch" />
-
     <gseealso glosid="performance_schema" />
 
   </glossent>

@@ -4519,7 +3815,6 @@
   <glossent id="non_blocking_io">
 
     <gterm>non-blocking I/O</gterm>
-
     <def>
 
       <para>

@@ -4528,7 +3823,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="asynchronous_io" />
 
   </glossent>

@@ -4536,7 +3830,6 @@
   <glossent id="non_repeatable_read">
 
     <gterm>non-repeatable read</gterm>
-
     <def>
 
       <para>

@@ -4545,14 +3838,12 @@
         data, but the queries return different results (changed by
         another transaction committing in the meantime).
       </para>
-
       <para>
         This kind of operation goes against the
         <emphasis role="bold">ACID</emphasis> principle of database
         design. Within a transaction, data should be consistent, with
         predictable and stable relationships.
       </para>
-
       <para>
         Among different <emphasis role="bold">isolation
         levels</emphasis>, non-repeatable reads are prevented by the

@@ -4563,21 +3854,13 @@
       </para>
 
     </def>
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="repeatable_read" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="serializable_read" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="read_uncommitted" />
-
     <gseealso glosid="acid" />
 
   </glossent>

@@ -4585,7 +3868,6 @@
   <glossent id="normalized">
 
     <gterm>normalized</gterm>
-
     <def>
 
       <para>

@@ -4594,7 +3876,6 @@
         ID, to avoid storing, querying, and updating redundant or
         lengthy values.
       </para>
-
       <para>
         For example, an address might be given a unique ID, so that a
         census database could represent the relationship

@@ -4603,7 +3884,6 @@
         storing multiple copies of a complex value such as
         <emphasis role="bold">123 Main Street, Anytown, USA</emphasis>.
       </para>
-
       <para>
         For another example, although a simple address book application
         might store each phone number in the same table as a person's

@@ -4612,7 +3892,6 @@
         table. This normalized representation could simplify large-scale
         updates when area codes split apart.
       </para>
-
       <para>
         Normalization is not always recommended. Data that is primarily
         queried, and only updated by deleting entirely and reloading, is

@@ -4623,9 +3902,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="relational" />
-
     <gseealso glosid="foreign_key" />
 
   </glossent>

@@ -4633,7 +3910,6 @@
   <glossent id="null">
 
     <gterm>NULL</gterm>
-
     <def>
 
       <para>

@@ -4649,7 +3925,6 @@
         <literal>NULL</literal> values uses the SQL idioms <literal>IS
         NULL</literal> or <literal>IS NOT NULL</literal>.
       </para>
-
       <para>
         <literal>NULL</literal> values play a part in index operations,
         because for performance a database must minimize the overhead of

@@ -4665,7 +3940,6 @@
         index, allowing for better query optimization (accurate counting
         of rows and estimation of whether to use the index).
       </para>
-
       <para>
         Because the <emphasis role="bold">primary key</emphasis> must be
         able to uniquely identify every row in the table, a

@@ -4674,7 +3948,6 @@
         cannot contain any rows with <literal>NULL</literal> values in
         all columns.
       </para>
-
       <para>
         Although the Oracle database allows a <literal>NULL</literal>
         value to be concatenated with a string, InnoDB treats the result

@@ -4682,11 +3955,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="sql" />
-
     <gseealso glosid="index" />
-
     <gseealso glosid="primary_key" />
 
   </glossent>

@@ -4694,7 +3964,6 @@
   <glossent id="off_page_column">
 
     <gterm>off-page column</gterm>
-
     <def>
 
       <para>

@@ -4706,9 +3975,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="overflow_page" />
-
     <gseealso glosid="b_tree" />
 
   </glossent>

@@ -4716,7 +3983,6 @@
   <glossent id="oltp">
 
     <gterm>OLTP</gterm>
-
     <def>
 
       <para>

@@ -4734,13 +4000,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="dml" />
-
     <gseealso glosid="query" />
-
     <gseealso glosid="data_warehouse" />
 
   </glossent>

@@ -4748,7 +4010,6 @@
   <glossent id="opt_file">
 
     <gterm>.OPT file</gterm>
-
     <def>
 
       <para>

@@ -4760,9 +4021,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
 
   </glossent>

@@ -4770,7 +4029,6 @@
   <glossent id="optimistic">
 
     <gterm>optimistic</gterm>
-
     <def>
 
       <para>

@@ -4788,7 +4046,6 @@
         does little unnecessary work; when requests do fail, extra work
         must be done to clean up and undo changes.
       </para>
-
       <para>
         InnoDB uses optimistic strategies for operations such as
         <emphasis role="bold">locking</emphasis> and

@@ -4798,7 +4055,6 @@
         requiring more work to undo the changes if the transaction is
         rolled back.
       </para>
-
       <para>
         The opposite of an optimistic strategy is a
         <emphasis role="bold">pessimistic</emphasis> one, where a system

@@ -4809,11 +4065,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="pessimistic" />
 
   </glossent>

@@ -4821,13 +4074,11 @@
   <glossent id="option">
 
     <gterm>option</gterm>
-
     <def>
 
       <para>
         A configuration parameter for MySQL.
       </para>
-
       <para>
         In the context of the InnoDB storage engine (either the built-in
         InnoDB or the InnoDB Plugin), each option name starts with the

@@ -4835,11 +4086,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="option_file" />
-
     <gseealso glosid="built_in" />
-
     <gseealso glosid="plugin" />
 
   </glossent>

@@ -4847,7 +4095,6 @@
   <glossent id="option_file">
 
     <gterm>option file</gterm>
-
     <def>
 
       <para>

@@ -4857,9 +4104,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="configuration_file" />
-
     <gseealso glosid="my_cnf" />
 
   </glossent>

@@ -4867,7 +4112,6 @@
   <glossent id="overflow_page">
 
     <gterm>overflow page</gterm>
-
     <def>
 
       <para>

@@ -4880,11 +4124,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="page" />
-
     <gseealso glosid="b_tree" />
-
     <gseealso glosid="off_page_column" />
 
   </glossent>

@@ -4892,7 +4133,6 @@
   <glossent id="parent_table">
 
     <gterm>parent table</gterm>
-
     <def>
 
       <para>

@@ -4909,9 +4149,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="foreign_key" />
-
     <gseealso glosid="child_table" />
 
   </glossent>

@@ -4919,7 +4157,6 @@
   <glossent id="partial_index">
 
     <gterm>partial index</gterm>
-
     <def>
 
       <para>

@@ -4930,9 +4167,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="index_prefix" />
 
   </glossent>

@@ -4940,7 +4175,6 @@
   <glossent id="par_file">
 
     <gterm>.PAR file</gterm>
-
     <def>
 
       <para>

@@ -4952,9 +4186,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
 
   </glossent>

@@ -4962,7 +4194,6 @@
   <glossent id="performance_schema">
 
     <gterm>Performance Schema</gterm>
-
     <def>
 
       <para>

@@ -4973,11 +4204,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="latch" />
-
     <gseealso glosid="rw_lock" />
-
     <gseealso glosid="mutex" />
 
   </glossent>

@@ -4985,7 +4213,6 @@
   <glossent id="pessimistic">
 
     <gterm>pessimistic</gterm>
-
     <def>
 
       <para>

@@ -5000,18 +4227,14 @@
         strategy of acquiring all locks needed by a transaction at the
         very beginning.
       </para>
-
       <para>
         Many built-in database mechanisms use the opposite
         <emphasis role="bold">optimistic</emphasis> methodology.
       </para>
 
     </def>
-
     <gseealso glosid="optimistic" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="deadlock" />
 
   </glossent>

@@ -5019,7 +4242,6 @@
   <glossent id="physical_backup">
 
     <gterm>physical backup</gterm>
-
     <def>
 
       <para>

@@ -5032,11 +4254,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="backup" />
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="logical_backup" />
 
   </glossent>

@@ -5044,7 +4263,6 @@
   <glossent id="pitr">
 
     <gterm>PITR backup</gterm>
-
     <def>
 
       <para>

@@ -5053,7 +4271,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="point_in_time_recovery" />
 
   </glossent>

@@ -5061,7 +4278,6 @@
   <glossent id="point_in_time_recovery">
 
     <gterm>point-in-time recovery</gterm>
-
     <def>
 
       <para>

@@ -5081,15 +4297,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="backup" />
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="logical_backup" />
-
     <gseealso glosid="physical_backup" />
-
     <gseealso glosid="pitr" />
 
   </glossent>

@@ -5097,7 +4308,6 @@
   <glossent id="prepared_backup">
 
     <gterm>prepared backup</gterm>
-
     <def>
 
       <para>

@@ -5113,17 +4323,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="binary_log" />
-
     <gseealso glosid="incremental_backup" />
-
     <gseealso glosid="restore" />
-
     <gseealso glosid="raw_backup" />
 
   </glossent>

@@ -5131,7 +4335,6 @@
   <glossent id="primary_key">
 
     <gterm>primary key</gterm>
-
     <def>
 
       <para>

@@ -5140,7 +4343,6 @@
         table. As such, it must be a unique index that does not contain
         any <literal>NULL</literal> values.
       </para>
-
       <para>
         InnoDB requires that every table has such an index (also called
         the <emphasis role="bold">clustered index</emphasis> or

@@ -5149,9 +4351,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="clustered_index" />
-
     <gseealso glosid="index" />
 
   </glossent>

@@ -5159,7 +4359,6 @@
   <glossent id="pthreads">
 
     <gterm>Pthreads</gterm>
-
     <def>
 
       <para>

@@ -5170,7 +4369,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="mutex" />
 
   </glossent>

@@ -5178,7 +4376,6 @@
   <glossent id="page">
 
     <gterm>page</gterm>
-
     <def>
 
       <para>

@@ -5191,20 +4388,15 @@
         structures so that the information about the row can be stored
         in one page.
       </para>
-
       <para>
         One way to fit more data in each page is to use
         <emphasis role="bold">compressed row format</emphasis>.
       </para>
 
     </def>
-
     <gseealso glosid="data_files" />
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="page_size" />
-
     <gseealso glosid="compressed_row_format" />
 
   </glossent>

@@ -5212,7 +4404,6 @@
   <glossent id="page_size">
 
     <gterm>page size</gterm>
-
     <def>
 
       <para>

@@ -5224,7 +4415,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="page" />
 
   </glossent>

@@ -5232,7 +4422,6 @@
   <glossent id="plugin">
 
     <gterm>plugin</gterm>
-
     <def>
 
       <para>

@@ -5248,7 +4437,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="built_in" />
 
   </glossent>

@@ -5256,13 +4444,11 @@
   <glossent id="predicate_locking">
 
     <gterm>predicate locking</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="locking" />
 
   </glossent>

@@ -5270,7 +4456,6 @@
   <glossent id="pseudo_record">
 
     <gterm>pseudo-record</gterm>
-
     <def>
 
       <para>

@@ -5280,11 +4465,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="supremum_record" />
-
     <gseealso glosid="infimum_record" />
 
   </glossent>

@@ -5292,7 +4474,6 @@
   <glossent id="purge">
 
     <gterm>purge</gterm>
-
     <def>
 
       <para>

@@ -5304,11 +4485,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="delete" />
-
     <gseealso glosid="crash_recovery" />
-
     <gseealso glosid="doublewrite_buffer" />
 
   </glossent>

@@ -5316,7 +4494,6 @@
   <glossent id="purge_buffering">
 
     <gterm>purge buffering</gterm>
-
     <def>
 
       <para>

@@ -5334,13 +4511,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="change_buffering" />
-
     <gseealso glosid="insert_buffer" />
-
     <gseealso glosid="insert_buffering" />
-
     <gseealso glosid="delete_buffering" />
 
   </glossent>

@@ -5348,7 +4521,6 @@
   <glossent id="purge_thread">
 
     <gterm>purge thread</gterm>
-
     <def>
 
       <para>

@@ -5358,9 +4530,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="thread" />
-
     <gseealso glosid="purge" />
 
   </glossent>

@@ -5368,7 +4538,6 @@
   <glossent id="phantom">
 
     <gterm>phantom</gterm>
-
     <def>
 
       <para>

@@ -5379,7 +4548,6 @@
         so that it matches the <literal>WHERE</literal> clause of the
         query.
       </para>
-
       <para>
         This occurrence is known as a phantom read. It is harder to
         guard against than a <emphasis role="bold">non-repeatable

@@ -5387,7 +4555,6 @@
         query result set does not prevent the changes that cause the
         phantom to appear.
       </para>
-
       <para>
         Among different <emphasis role="bold">isolation
         levels</emphasis>, phantom reads are prevented by the

@@ -5398,19 +4565,12 @@
       </para>
 
     </def>
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="serializable_read" />
-
     <gseealso glosid="non_repeatable_read" />
-
     <gseealso glosid="repeatable_read" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="read_uncommitted" />
 
   </glossent>

@@ -5418,7 +4578,6 @@
   <glossent id="prefix">
 
     <gterm>prefix</gterm>
-
     <gsee glosid="index_prefix" />
 
   </glossent>

@@ -5426,7 +4585,6 @@
   <glossent id="query">
 
     <gterm>query</gterm>
-
     <def>
 
       <para>

@@ -5437,20 +4595,15 @@
         might be optimized by consulting an
         <emphasis role="bold">index</emphasis>.
       </para>
-
       <para>
         Normally with MySQL, queries are coded using SQL. (Even if you
         are using some other language for the main application logic.)
       </para>
 
     </def>
-
     <gseealso glosid="table" />
-
     <gseealso glosid="database" />
-
     <gseealso glosid="index" />
-
     <gseealso glosid="sql" />
 
   </glossent>

@@ -5458,7 +4611,6 @@
   <glossent id="raid">
 
     <gterm>RAID</gterm>
-
     <def>
 
       <para>

@@ -5470,7 +4622,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="concurrency" />
 
   </glossent>

@@ -5478,7 +4629,6 @@
   <glossent id="raw_backup">
 
     <gterm>raw backup</gterm>
-
     <def>
 
       <para>

@@ -5494,19 +4644,12 @@
       </para>
 
     </def>
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="binary_log" />
-
     <gseealso glosid="ibbackup_logfile" />
-
     <gseealso glosid="incremental_backup" />
-
     <gseealso glosid="restore" />
-
     <gseealso glosid="prepared_backup" />
 
   </glossent>

@@ -5514,7 +4657,6 @@
   <glossent id="read_ahead">
 
     <gterm>read-ahead</gterm>
-
     <def>
 
       <para>

@@ -5524,7 +4666,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_cache" />
 
   </glossent>

@@ -5532,7 +4673,6 @@
   <glossent id="redo_log">
 
     <gterm>redo log</gterm>
-
     <def>
 
       <para>

@@ -5544,7 +4684,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="ib_logfile" />
 
   </glossent>

@@ -5552,7 +4691,6 @@
   <glossent id="redundant_row_format">
 
     <gterm>redundant row format</gterm>
-
     <def>
 
       <para>

@@ -5563,9 +4701,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="row_format" />
-
     <gseealso glosid="compact_row_format" />
 
   </glossent>

@@ -5573,13 +4709,11 @@
   <glossent id="relational">
 
     <gterm>relational</gterm>
-
     <def>
 
       <para>
         An important aspect of modern database systems.
       </para>
-
       <para>
         In a mathematical context, the relations within a database are
         derived from set theory. For example, the <literal>OR</literal>

@@ -5587,7 +4721,6 @@
         <literal>WHERE</literal> clause represent the notions of union
         and intersection.
       </para>
-
       <para>
         In everyday terms, the database encodes and enforces
         relationships such as one-to-one, one-to-many, many-to-one, and

@@ -5598,7 +4731,6 @@
         taxpayer ID, and any taxpayer ID could only be associated with
         one person.
       </para>
-
       <para>
         At the database level, these relationships are expressed through
         SQL features such as columns within a table, unique and

@@ -5611,11 +4743,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="foreign_key" />
-
     <gseealso glosid="normalized" />
 
   </glossent>

@@ -5623,7 +4752,6 @@
   <glossent id="restore">
 
     <gterm>restore</gterm>
-
     <def>
 
       <para>

@@ -5640,17 +4768,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="prepared_backup" />
-
     <gseealso glosid="replication" />
-
     <gseealso glosid="slave_database" />
-
     <gseealso glosid="innobackup_command" />
 
   </glossent>

@@ -5658,7 +4780,6 @@
   <glossent id="row_format">
 
     <gterm>row format</gterm>
-
     <def>
 
       <para>

@@ -5667,7 +4788,6 @@
         formats are introduced to support the resulting improvements in
         storage efficiency and performance.
       </para>
-
       <para>
         Each table has its own row format, specified through the
         <literal>ROW_FORMAT</literal> option. To see the row format for

@@ -5680,15 +4800,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="fixed_row_format" />
-
     <gseealso glosid="dynamic_row_format" />
-
     <gseealso glosid="compact_row_format" />
-
     <gseealso glosid="redundant_row_format" />
-
     <gseealso glosid="compressed_row_format" />
 
   </glossent>

@@ -5696,7 +4811,6 @@
   <glossent id="random_dive">
 
     <gterm>random dive</gterm>
-
     <def>
 
       <para>

@@ -5706,13 +4820,11 @@
         the number of different values. This operation occurs when each
         table is first opened.
       </para>
-
       <para>
         Originally, the number of sampled pages was fixed at 8; now, it
         is determined by the setting of the
         <literal>innodb_stats_sample_pages</literal> parameter.
       </para>
-
       <para>
         The way the random pages are picked depends on the setting of
         the innodb_use_legacy_cardinality_algorithm parameter. The

@@ -5721,7 +4833,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="cardinality" />
 
   </glossent>

@@ -5729,7 +4840,6 @@
   <glossent id="referential_integrity">
 
     <gterm>referential integrity</gterm>
-
     <def>
 
       <para>

@@ -5742,9 +4852,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="foreign_key" />
 
   </glossent>

@@ -5752,7 +4860,6 @@
   <glossent id="row_based_replication">
 
     <gterm>row-based replication</gterm>
-
     <def>
 
       <para>

@@ -5763,13 +4870,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="replication" />
-
     <gseealso glosid="statement_based_replication" />
-
     <gseealso glosid="auto_increment_locking" />
-
     <gseealso glosid="innodb_autoinc_lock_mode" />
 
   </glossent>

@@ -5777,7 +4880,6 @@
   <glossent id="read_uncommitted">
 
     <gterm>read uncommitted</gterm>
-
     <def>
 
       <para>

@@ -5797,15 +4899,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="dirty_read" />
 
   </glossent>

@@ -5813,7 +4910,6 @@
   <glossent id="read_committed">
 
     <gterm>read committed</gterm>
-
     <def>
 
       <para>

@@ -5826,7 +4922,6 @@
         bad data, but the data that it does see may depend to some
         extent on the timing of other transactions.
       </para>
-
       <para>
         When a transaction with this isolation level performs
         <literal>UPDATE ... WHERE</literal> or <literal>DELETE ...

@@ -5837,17 +4932,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="repeatable_read" />
-
     <gseealso glosid="serializable_read" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="acid" />
 
   </glossent>

@@ -5855,7 +4944,6 @@
   <glossent id="repeatable_read">
 
     <gterm>repeatable read</gterm>
-
     <def>
 
       <para>

@@ -5869,7 +4957,6 @@
         the same snapshot, that is, the data as it was at the time the
         transaction started.
       </para>
-
       <para>
         When a transaction with this isolation level performs
         <literal>UPDATE ... WHERE</literal>, <literal>DELETE ...

@@ -5879,17 +4966,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="serializable_read" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="acid" />
 
   </glossent>

@@ -5897,13 +4978,11 @@
   <glossent id="record_only_lock">
 
     <gterm>record-only lock</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="locking" />
 
   </glossent>

@@ -5911,7 +4990,6 @@
   <glossent id="replication">
 
     <gterm>replication</gterm>
-
     <def>
 
       <para>

@@ -5928,13 +5006,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="master_database" />
-
     <gseealso glosid="slave_database" />
-
     <gseealso glosid="row_based_replication" />
-
     <gseealso glosid="statement_based_replication" />
 
   </glossent>

@@ -5942,7 +5016,6 @@
   <glossent id="rollback">
 
     <gterm>rollback</gterm>
-
     <def>
 
       <para>

@@ -5952,7 +5025,6 @@
         <emphasis role="bold">commit</emphasis>, which makes permanent
         any changes made in the transaction.
       </para>
-
       <para>
         By default, MySQL uses the
         <emphasis role="bold">autocommit</emphasis> setting, which

@@ -5962,11 +5034,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="transaction" />
 
   </glossent>

@@ -5974,7 +5043,6 @@
   <glossent id="rollback_segment">
 
     <gterm>rollback segment</gterm>
-
     <def>
 
       <para>

@@ -5984,9 +5052,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="undo_log" />
-
     <gseealso glosid="system_tablespace" />
 
   </glossent>

@@ -5994,7 +5060,6 @@
   <glossent id="row_lock">
 
     <gterm>row lock</gterm>
-
     <def>
 
       <para>

@@ -6004,11 +5069,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="lock_mode" />
-
     <gseealso glosid="transaction" />
 
   </glossent>

@@ -6016,7 +5078,6 @@
   <glossent id="rw_lock">
 
     <gterm>rw-lock</gterm>
-
     <def>
 
       <para>

@@ -6031,13 +5092,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="latch" />
-
     <gseealso glosid="performance_schema" />
-
     <gseealso glosid="mutex" />
 
   </glossent>

@@ -6045,7 +5102,6 @@
   <glossent id="savepoint">
 
     <gterm>savepoint</gterm>
-
     <def>
 
       <para>

@@ -6061,9 +5117,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="rollback" />
 
   </glossent>

@@ -6071,7 +5125,6 @@
   <glossent id="secondary_index">
 
     <gterm>secondary index</gterm>
-
     <def>
 
       <para>

@@ -6082,7 +5135,6 @@
         required for each InnoDB table, and stores the data for all the
         table columns.)
       </para>
-
       <para>
         A secondary index can be used to satisfy queries that only
         require values from the indexed columns. For more complex

@@ -6090,7 +5142,6 @@
         table, which are then retrieved through lookups using the
         clustered index.
       </para>
-
       <para>
         Creating and dropping secondary indexes has traditionally
         involved significant overhead from copying all the data in the

@@ -6102,11 +5153,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="index" />
-
     <gseealso glosid="clustered_index" />
-
     <gseealso glosid="fast_index_creation" />
 
   </glossent>

@@ -6114,7 +5162,6 @@
   <glossent id="schema">
 
     <gterm>schema</gterm>
-
     <def>
 
       <para>

@@ -6126,14 +5173,12 @@
         Ideally, they are also connected logically, working together as
         part of a unified application or flexible framework.
       </para>
-
       <para>
         In MySQL, physically, a <emphasis role="bold">schema</emphasis>
         is analogous to a <emphasis role="bold">database</emphasis>.
         Typically, all the objects for a MySQL application are contained
         within a single database.
       </para>
-
       <para>
         Some other database products draw a distinction. For example, in
         the Oracle Database product, a

@@ -6143,11 +5188,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="database" />
-
     <gseealso glosid="information_schema" />
-
     <gseealso glosid="ib_file_set" />
 
   </glossent>

@@ -6155,7 +5197,6 @@
   <glossent id="semi_consistent_read">
 
     <gterm>semi-consistent read</gterm>
-
     <def>
 
       <para>

@@ -6176,11 +5217,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="read_committed" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="isolation_level" />
 
   </glossent>

@@ -6188,7 +5226,6 @@
   <glossent id="server">
 
     <gterm>server</gterm>
-
     <def>
 
       <para>

@@ -6202,9 +5239,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="client" />
-
     <gseealso glosid="mysqld" />
 
   </glossent>

@@ -6212,7 +5247,6 @@
   <glossent id="selectivity">
 
     <gterm>selectivity</gterm>
-
     <def>
 
       <para>

@@ -6227,7 +5261,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="cardinality" />
 
   </glossent>

@@ -6235,7 +5268,6 @@
   <glossent id="shared_tablespace">
 
     <gterm>shared tablespace</gterm>
-
     <def>
 
       <para>

@@ -6244,7 +5276,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="system_tablespace" />
 
   </glossent>

@@ -6252,7 +5283,6 @@
   <glossent id="shutdown">
 
     <gterm>shutdown</gterm>
-
     <def>
 
       <para>

@@ -6263,16 +5293,13 @@
         <emphasis role="bold">fast</emphasis> to shut down but must do
         the cleanup the next time it starts.
       </para>
-
       <para>
         The shutdown mode is controlled by the
         <literal>innodb_fast_shutdown</literal> option.
       </para>
 
     </def>
-
     <gseealso glosid="slow_shutdown" />
-
     <gseealso glosid="fast_shutdown" />
 
   </glossent>

@@ -6280,19 +5307,15 @@
   <glossent id="slow_shutdown">
 
     <gterm>slow shutdown</gterm>
-
     <def>
 
       <para>
         A type of shutdown that does additional flushing operations
         before completing. Specified by the configuration parameter
         <literal>innodb_fast_shutdown=0</literal>.
-
 <!-- <programlisting>SET GLOBAL innodb_fast_shutdown=0;</programlisting> -->
-
         Although the shutdown itself can take longer, that time will be
         saved on the subsequent startup.
-
 <!--
 Referenced in installation section of Plugin doc,
 but command or parameters not shown on first use.

@@ -6303,9 +5326,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="shutdown" />
-
     <gseealso glosid="fast_shutdown" />
 
   </glossent>

@@ -6313,7 +5334,6 @@
   <glossent id="ssd">
 
     <gterm>SSD</gterm>
-
     <def>
 
       <para>

@@ -6325,7 +5345,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="disk_based" />
 
   </glossent>

@@ -6333,7 +5352,6 @@
   <glossent id="strict_mode">
 
     <gterm>strict mode</gterm>
-
     <def>
 
       <para>

@@ -6347,13 +5365,11 @@
         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>

@@ -6361,7 +5377,6 @@
   <glossent id="sublist">
 
     <gterm>sublist</gterm>
-
     <def>
 
       <para>

@@ -6373,13 +5388,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
-
     <gseealso glosid="eviction" />
-
     <gseealso glosid="list" />
-
     <gseealso glosid="lru" />
 
   </glossent>

@@ -6387,7 +5398,6 @@
   <glossent id="storage_engine">
 
     <gterm>storage engine</gterm>
-
     <def>
 
       <para>

@@ -6399,7 +5409,6 @@
         usage, read speed versus write speed, and speed versus
         robustness.
       </para>
-
       <para>
         The <emphasis role="bold">MySQL Enterprise Backup</emphasis>
         product is optimized for backing up tables produced by the

@@ -6409,9 +5418,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="innodb" />
-
     <gseealso glosid="mysql_enterprise_backup" />
 
   </glossent>

@@ -6419,7 +5426,6 @@
   <glossent id="scalability">
 
     <gterm>scalability</gterm>
-
     <def>
 
       <para>

@@ -6442,7 +5448,6 @@
   <glossent id="statement_based_replication">
 
     <gterm>statement-based replication</gterm>
-
     <def>
 
       <para>

@@ -6454,13 +5459,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="replication" />
-
     <gseealso glosid="auto_increment_locking" />
-
     <gseealso glosid="innodb_autoinc_lock_mode" />
-
     <gseealso glosid="row_based_replication" />
 
   </glossent>

@@ -6468,7 +5469,6 @@
   <glossent id="serializable_read">
 
     <gterm>serializable read</gterm>
-
     <def>
 
       <para>

@@ -6482,7 +5482,6 @@
         start of the current transaction, cause the current transaction
         to wait.
       </para>
-
       <para>
         This is the default isolation level specified by the SQL
         standard. In practice, this degree of strictness is rarely

@@ -6491,17 +5490,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="repeatable_read" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="isolation_level" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="acid" />
 
   </glossent>

@@ -6509,7 +5502,6 @@
   <glossent id="supremum_record">
 
     <gterm>supremum record</gterm>
-
     <def>
 
       <para>

@@ -6523,11 +5515,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="gap" />
-
     <gseealso glosid="infimum_record" />
-
     <gseealso glosid="pseudo_record" />
 
   </glossent>

@@ -6535,7 +5524,6 @@
   <glossent id="shared_lock">
 
     <gterm>shared lock</gterm>
-
     <def>
 
       <para>

@@ -6547,11 +5535,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="exclusive_lock" />
 
   </glossent>

@@ -6559,7 +5544,6 @@
   <glossent id="slave_database">
 
     <gterm>slave database</gterm>
-
     <def>
 
       <para>

@@ -6571,7 +5555,6 @@
         those same changes. Thus it maintains the same contents as the
         master, although it might lag somewhat behind.
       </para>
-
       <para>
         In MySQL, slave databases are commonly used in disaster
         recovery, to take the place of a master database that fails.

@@ -6581,9 +5564,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="replication" />
-
     <gseealso glosid="master_database" />
 
   </glossent>

@@ -6591,7 +5572,6 @@
   <glossent id="__sleep">
 
     <gterm>--sleep</gterm>
-
     <def>
 
       <para>

@@ -6607,13 +5587,11 @@
   <glossent id="space_id">
 
     <gterm>space ID</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="tablespace" />
 
   </glossent>

@@ -6621,7 +5599,6 @@
   <glossent id="sql">
 
     <gterm>SQL</gterm>
-
     <def>
 
       <para>

@@ -6633,11 +5610,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="ddl" />
-
     <gseealso glosid="dml" />
-
     <gseealso glosid="query" />
 
   </glossent>

@@ -6645,7 +5619,6 @@
   <glossent id="stored_procedure">
 
     <gterm>stored procedure</gterm>
-
     <def>
 
       <para></para>

@@ -6657,7 +5630,6 @@
   <glossent id="system_tablespace">
 
     <gterm>system tablespace</gterm>
-
     <def>
 
       <para>

@@ -6665,7 +5637,6 @@
         a database, as well as all the metadata for InnoDB-related
         objects (the <emphasis role="bold">data dictionary</emphasis>).
       </para>
-
       <para>
         Turning on the
         <emphasis role="bold">innodb_file_per_table</emphasis> option

@@ -6673,7 +5644,6 @@
         <emphasis role="bold">tablespace</emphasis>, reducing the size
         of, and dependencies on, the system tablespace.
       </para>
-
       <para>
         Keeping all table data in the system tablespace has implications
         for the <emphasis role="bold">MySQL Enterprise Backup</emphasis>

@@ -6684,19 +5654,12 @@
       </para>
 
     </def>
-
     <gseealso glosid="data_dictionary" />
-
     <gseealso glosid="file_per_table" />
-
     <gseealso glosid="innodb_file_per_table" />
-
     <gseealso glosid="ibdata_file" />
-
     <gseealso glosid="tablespace" />
-
     <gseealso glosid="file_format" />
-
     <gseealso glosid="barracuda" />
 
   </glossent>

@@ -6704,7 +5667,6 @@
   <glossent id="table">
 
     <gterm>table</gterm>
-
     <def>
 
       <para>

@@ -6716,13 +5678,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="clustered_index" />
-
     <gseealso glosid="file_per_table" />
-
     <gseealso glosid="table" />
-
     <gseealso glosid="system_tablespace" />
 
   </glossent>

@@ -6730,7 +5688,6 @@
   <glossent id="table_lock">
 
     <gterm>table lock</gterm>
-
     <def>
 
       <para>

@@ -6749,21 +5706,13 @@
       </para>
 
     </def>
-
     <gseealso glosid="table" />
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="locking" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="row_lock" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="dml" />
-
     <gseealso glosid="query" />
 
   </glossent>

@@ -6771,7 +5720,6 @@
   <glossent id="tablespace">
 
     <gterm>tablespace</gterm>
-
     <def>
 
       <para>

@@ -6783,7 +5731,6 @@
         option allows newly created tables to each have their own
         tablespace, with a separate data file for each table.
       </para>
-
       <para>
         Tablespaces created by the built-in InnoDB storage engine are
         upward compatible with the InnoDB Plugin. Tablespaces created by

@@ -6793,21 +5740,13 @@
       </para>
 
     </def>
-
     <gseealso glosid="file_per_table" />
-
     <gseealso glosid="innodb_file_per_table" />
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="data_dictionary" />
-
     <gseealso glosid="ibdata_file" />
-
     <gseealso glosid="antelope" />
-
     <gseealso glosid="barracuda" />
-
     <gseealso glosid="compressed_row_format" />
 
   </glossent>

@@ -6815,7 +5754,6 @@
   <glossent id="tablespace_dictionary">
 
     <gterm>tablespace dictionary</gterm>
-
     <def>
 
       <para>

@@ -6833,17 +5771,11 @@
       </para>
 
     </def>
-
     <gseealso glosid="tablespace" />
-
     <gseealso glosid="data_dictionary" />
-
     <gseealso glosid="frm_file" />
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="ibd_file" />
-
     <gseealso glosid="file_per_table" />
 
   </glossent>

@@ -6851,7 +5783,6 @@
   <glossent id="temporary_table">
 
     <gterm>temporary table</gterm>
-
     <def>
 
       <para>

@@ -6864,7 +5795,6 @@
         tables, by being less scrupulous about writing data to disk and
         other measures to protect the data across restarts.
       </para>
-
       <para>
         Sometimes, the data itself is removed automatically at a set
         time, such as when the transaction ends or when the session

@@ -6873,73 +5803,70 @@
       </para>
 
     </def>
-
     <gseealso glosid="table" />
 
   </glossent>
 
-  <glossent id="thread">
+  <glossent id="table_monitor">
 
-    <gterm>thread</gterm>
-
+    <gterm>table monitor</gterm>
     <def>
 
       <para></para>
 
     </def>
+    <gseealso glosid="monitor" />
 
-    <gseealso glosid="master_thread" />
-
-    <gseealso glosid="pthreads" />
-
   </glossent>
 
-  <glossent id="table_monitor">
+  <glossent id="tablespace_monitor">
 
-    <gterm>table monitor</gterm>
-
+    <gterm>tablespace monitor</gterm>
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="monitor" />
 
   </glossent>
 
-  <glossent id="tablespace_monitor">
+  <glossent id="thread">
 
-    <gterm>tablespace monitor</gterm>
-
+    <gterm>thread</gterm>
     <def>
 
       <para></para>
 
     </def>
+    <gseealso glosid="master_thread" />
+    <gseealso glosid="pthreads" />
 
-    <gseealso glosid="monitor" />
-
   </glossent>
 
-  <glossent id="trigger">
+  <glossent id="torn_page">
 
-    <gterm>trigger</gterm>
-
+    <gterm>torn page</gterm>
     <def>
 
-      <para></para>
+      <para>
+        An error condition that can occur due to a combination of I/O
+        device configuration and hardware failure. If data is written
+        out in chunks smaller than the InnoDB page size (typically
+        16KB), a hardware failure while writing could result in only
+        part of a page being stored to disk. The InnoDB
+        <emphasis role="bold">doublewrite buffer</emphasis> guards
+        against this possibility.
+      </para>
 
     </def>
+    <gseealso glosid="doublewrite_buffer" />
 
-    <gseealso glosid="stored_procedure" />
-
   </glossent>
 
   <glossent id="trg_file">
 
     <gterm>.TRG file</gterm>
-
     <def>
 
       <para>

@@ -6951,19 +5878,27 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
-
     <gseealso glosid="trn_file" />
 
   </glossent>
 
+  <glossent id="trigger">
+
+    <gterm>trigger</gterm>
+    <def>
+
+      <para></para>
+
+    </def>
+    <gseealso glosid="stored_procedure" />
+
+  </glossent>
+
   <glossent id="trn_file">
 
     <gterm>.TRN file</gterm>
-
     <def>
 
       <para>

@@ -6975,11 +5910,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="mysql_enterprise_backup" />
-
     <gseealso glosid="innobackup_command" />
-
     <gseealso glosid="trg_file" />
 
   </glossent>

@@ -6987,7 +5919,6 @@
   <glossent id="two_phase_commit">
 
     <gterm>two-phase commit</gterm>
-
     <def>
 
       <para>

@@ -7002,13 +5933,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="xa" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="rollback" />
 
   </glossent>

@@ -7016,13 +5943,11 @@
   <glossent id="two_phase_locking">
 
     <gterm>two-phase locking</gterm>
-
     <def>
 
       <para></para>
 
     </def>
-
     <gseealso glosid="xa" />
 
   </glossent>

@@ -7030,7 +5955,6 @@
   <glossent id="transaction">
 
     <gterm>transaction</gterm>
-
     <def>
 
       <para>

@@ -7040,7 +5964,6 @@
         committed, or all the changes are undone when the transaction is
         rolled back.
       </para>
-
       <para>
         Database transactions, as implemented by InnoDB, have properties
         that are collectively known by the acronym

@@ -7049,15 +5972,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="acid" />
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="rollback" />
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="isolation_level" />
 
   </glossent>

@@ -7065,7 +5983,6 @@
   <glossent id="transaction_id">
 
     <gterm>transaction ID</gterm>
-
     <def>
 
       <para>

@@ -7075,7 +5992,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="implicit_row_lock" />
 
   </glossent>

@@ -7083,7 +5999,6 @@
   <glossent id="transportable_tablespace">
 
     <gterm>transportable tablespace</gterm>
-
     <def>
 
       <para>

@@ -7104,15 +6019,10 @@
       </para>
 
     </def>
-
     <gseealso glosid="tablespace" />
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="file_per_table" />
-
     <gseealso glosid="ibd_file" />
-
     <gseealso glosid="space_id" />
 
   </glossent>

@@ -7120,7 +6030,6 @@
   <glossent id="troubleshooting">
 
     <gterm>troubleshooting</gterm>
-
     <def>
 
       <para>

@@ -7135,7 +6044,6 @@
   <glossent id="tuple">
 
     <gterm>tuple</gterm>
-
     <def>
 
       <para>

@@ -7148,13 +6056,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="cursor" />
-
     <gseealso glosid="read_tuple" />
-
     <gseealso glosid="read_write_tuple" />
-
     <gseealso glosid="search_tuple" />
 
   </glossent>

@@ -7162,7 +6066,6 @@
   <glossent id="truncate">
 
     <gterm>truncate</gterm>
-
     <def>
 
       <para>

@@ -7175,7 +6078,6 @@
         one. Because this is a DDL operation, it cannot be
         <emphasis role="bold">rolled back</emphasis>.
       </para>
-
       <para>
         If the table being truncated contains foreign keys that
         reference another table, the truncation operation uses a slower

@@ -7185,9 +6087,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="ddl" />
-
     <gseealso glosid="rollback" />
 
   </glossent>

@@ -7195,7 +6095,6 @@
   <glossent id="undo_buffer">
 
     <gterm>undo buffer</gterm>
-
     <gsee glosid="undo_log" />
 
   </glossent>

@@ -7203,7 +6102,6 @@
   <glossent id="undo_log">
 
     <gterm>undo log</gterm>
-
     <def>
 
       <para>

@@ -7222,13 +6120,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="consistent_read" />
-
     <gseealso glosid="system_tablespace" />
-
     <gseealso glosid="rollback_segment" />
 
   </glossent>

@@ -7236,7 +6130,6 @@
   <glossent id="undo">
 
     <gterm>undo</gterm>
-
     <def>
 
       <para>

@@ -7247,11 +6140,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="undo_log" />
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="rollback" />
 
   </glossent>

@@ -7259,7 +6149,6 @@
   <glossent id="unique_constraint">
 
     <gterm>unique constraint</gterm>
-
     <def>
 
       <para>

@@ -7274,11 +6163,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="constraint" />
-
     <gseealso glosid="relational" />
-
     <gseealso glosid="unique_index" />
 
   </glossent>

@@ -7286,7 +6172,6 @@
   <glossent id="unique_index">
 
     <gterm>unique index</gterm>
-
     <def>
 
       <para>

@@ -7302,11 +6187,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="unique_constraint" />
-
     <gseealso glosid="unique_key" />
-
     <gseealso glosid="cardinality" />
 
   </glossent>

@@ -7314,7 +6196,6 @@
   <glossent id="unique_key">
 
     <gterm>unique key</gterm>
-
     <def>
 
       <para>

@@ -7326,11 +6207,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="unique_constraint" />
-
     <gseealso glosid="unique_index" />
-
     <gseealso glosid="cardinality" />
 
   </glossent>

@@ -7338,7 +6216,6 @@
   <glossent id="victim">
 
     <gterm>victim</gterm>
-
     <def>
 
       <para>

@@ -7349,11 +6226,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="innodb_lock_wait_timeout" />
-
     <gseealso glosid="deadlock" />
-
     <gseealso glosid="deadlock_detection" />
 
   </glossent>

@@ -7361,7 +6235,6 @@
   <glossent id="wait">
 
     <gterm>wait</gterm>
-
     <def>
 
       <para>

@@ -7376,7 +6249,6 @@
         scheduling, operating system <literal>wait()</literal> calls,
         and short-duration spin loops.
       </para>
-
       <para>
         On systems with heavy load and many transactions, you might use
         the output from the <literal>SHOW INNODB STATUS</literal>

@@ -7386,13 +6258,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="lock" />
-
     <gseealso glosid="mutex" />
-
     <gseealso glosid="latch" />
-
     <gseealso glosid="concurrency" />
 
   </glossent>

@@ -7400,7 +6268,6 @@
   <glossent id="warm_backup">
 
     <gterm>warm backup</gterm>
-
     <def>
 
       <para>

@@ -7412,11 +6279,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="backup" />
-
     <gseealso glosid="hot_backup" />
-
     <gseealso glosid="cold_backup" />
 
   </glossent>

@@ -7424,7 +6288,6 @@
   <glossent id="warm_up">
 
     <gterm>warm up</gterm>
-
     <def>
 
       <para>

@@ -7438,7 +6301,6 @@
       </para>
 
     </def>
-
     <gseealso glosid="buffer_pool" />
 
   </glossent>

@@ -7446,14 +6308,12 @@
   <glossent id="windows">
 
     <gterm>Windows</gterm>
-
     <def>
 
       <para>
         The built-in InnoDB storage engine and the InnoDB Plugin are
         supported on all the same Microsoft Windows versions as MySQL.
       </para>
-
       <para>
         The <emphasis role="bold">MySQL Enterprise Backup</emphasis>
         product is available on Windows, although the

@@ -7468,7 +6328,6 @@
   <glossent id="workload">
 
     <gterm>workload</gterm>
-
     <def>
 
       <para>

@@ -7482,9 +6341,7 @@
       </para>
 
     </def>
-
     <gseealso glosid="sql" />
-
     <gseealso glosid="bottleneck" />
 
   </glossent>

@@ -7492,7 +6349,6 @@
   <glossent id="write_combining">
 
     <gterm>write combining</gterm>
-
     <def>
 
       <para>

@@ -7506,11 +6362,8 @@
       </para>
 
     </def>
-
     <gseealso glosid="dirty_page" />
-
     <gseealso glosid="flush" />
-
     <gseealso glosid="buffer_pool" />
 
   </glossent>

@@ -7518,7 +6371,6 @@
   <glossent id="xa">
 
     <gterm>XA</gterm>
-
     <def>
 
       <para>

@@ -7527,7 +6379,6 @@
         databases to participate in a transaction while maintaining
         <emphasis role="bold">ACID</emphasis> compliance.
       </para>
-
       <para>
         XA Distributed Transaction support is turned on by default. If
         you are not using this feature, note that it adds an extra fsync

@@ -7535,13 +6386,9 @@
       </para>
 
     </def>
-
     <gseealso glosid="transaction" />
-
     <gseealso glosid="commit" />
-
     <gseealso glosid="two_phase_locking" />
-
     <gseealso glosid="two_phase_commit" />
 
   </glossent>


Thread
svn commit - mysqldoc@docsrva: r24782 - trunk/dynamic-docs/glossaryjohn.russell12 Jan