List:Commits« Previous MessageNext Message »
From:john.russell Date:August 25 2010 6:59pm
Subject:svn commit - mysqldoc@docsrva: r22442 - trunk/innodb-plugin-1.1
View as plain text  
Author: jrussell
Date: 2010-08-25 20:59:06 +0200 (Wed, 25 Aug 2010)
New Revision: 22442

Log:
Turned some http links into regular cross-references.


Modified:
   trunk/innodb-plugin-1.1/innodb-downgrading.xml
   trunk/innodb-plugin-1.1/innodb-information-schema.xml
   trunk/innodb-plugin-1.1/innodb-other-changes.xml
   trunk/innodb-plugin-1.1/innodb-performance.xml
   trunk/innodb-plugin-1.1/innodb-plugin-introduction.xml
   trunk/innodb-plugin-1.1/innodb-upgrading.xml


Modified: trunk/innodb-plugin-1.1/innodb-downgrading.xml
===================================================================
--- trunk/innodb-plugin-1.1/innodb-downgrading.xml	2010-08-25 18:34:36 UTC (rev 22441)
+++ trunk/innodb-plugin-1.1/innodb-downgrading.xml	2010-08-25 18:59:06 UTC (rev 22442)
Changed blocks: 7, Lines Added: 19, Lines Deleted: 41; 4323 bytes

@@ -195,9 +195,7 @@
         In &mysql;, configuration options can be specified in the
         <literal>mysqld</literal> command line or the option file
         (<literal>my.cnf</literal> or <literal>my.ini</literal>). See
-        the MySQL manual on
-        <ulink url="http://dev.mysql.com/doc/refman/5.1/en/option-files.html">Using
-        Option Files</ulink> for more information.
+        <xref linkend="option-files"/> for more information.
       </para>
 
     </section>

@@ -244,11 +242,7 @@
 
       <para>
         Restart the server. For the details of the shutdown procedure,
-        see the MySQL manual on
-        <ulink
-      url="http://dev.mysql.com/doc/refman/5.1/en/server-shutdown.html"
-      >The
-        Shutdown Process</ulink>.
+        see <xref linkend="server-shutdown"/>.
       </para>
 
     </section>

@@ -273,14 +267,12 @@
         <emphasis role="strong">enable <quote>slow</quote>
         shutdown</emphasis>:
 
-<programlisting>SET GLOBAL innodb_fast_shutdown=0;</programlisting>
+<programlisting>
+SET GLOBAL innodb_fast_shutdown=0;
+</programlisting>
 
-        For the details of the shutdown procedure, see the MySQL manual
-        on
-        <ulink
-      url="http://dev.mysql.com/doc/refman/5.1/en/server-shutdown.html"
-      >The
-        Shutdown Process</ulink>.
+        For the details of the shutdown procedure, see
+        <xref linkend="server-shutdown"/>.
       </para>
 
     </section>

@@ -388,12 +380,8 @@
         log by setting &innodb_force_recovery;=3. However, this is not a
         recommended approach, since in addition to preventing the purge
         of old versions, this recovery mode prevents the rollback of
-        uncommitted transactions. For more information, see the MySQL
-        manual on
-        <ulink
-      url="http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html"
-      >Forcing
-        &innodb; Recovery</ulink>.
+        uncommitted transactions. For more information, see
+        <xref linkend="forcing-recovery"/>.
       </para>
 
       <para>

@@ -426,11 +414,8 @@
         recovery from the redo log by setting the parameter
         &innodb_force_recovery;=6. However, this is
         <emphasis role="strong">strongly discouraged</emphasis>, because
-        may lead into severe corruption. See the MySQL manual on
-        <ulink
-      url="http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html"
-      >Forcing
-        &innodb; Recovery</ulink> for more information.
+        it may lead into severe corruption. See
+        <xref linkend="forcing-recovery"/> for more information.
       </para>
 
     </section>

@@ -467,12 +452,8 @@
         recovery by setting &innodb_force_recovery;=6. However, this is
         <emphasis
       role="strong">strongly discouraged</emphasis>,
-        because it may lead into severe corruption. For more
-        information, see the MySQL manual on
-        <ulink
-      url="http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html"
-      >Forcing
-        &innodb; Recovery</ulink>.
+        because it may lead into severe corruption. See
+        <xref linkend="forcing-recovery"/> for more information.
       </para>
 
     </section>

@@ -525,15 +506,12 @@
       </para>
 
       <para>
-        To disable insert buffer merges, you may set
-        &innodb_force_recovery;=4 so that you can back up the
-        uncompressed tables with the &builtin;. Be sure not to use any
-        <literal>WHERE</literal> conditions that would require access to
-        secondary indexes. For more information, see the MySQL manual on
-        <ulink
-      url="http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html"
-      >Forcing
-        &innodb; Recovery</ulink>.
+        To disable insert buffer merges, set &innodb_force_recovery;=4
+        so that you can back up the uncompressed tables with the
+        &builtin;. Be sure not to use any <literal>WHERE</literal>
+        conditions that would require access to secondary indexes. For
+        more information, see <xref
+      linkend="forcing-recovery"/>.
       </para>
 
       <para>


Modified: trunk/innodb-plugin-1.1/innodb-information-schema.xml
===================================================================
--- trunk/innodb-plugin-1.1/innodb-information-schema.xml	2010-08-25 18:34:36 UTC (rev 22441)
+++ trunk/innodb-plugin-1.1/innodb-information-schema.xml	2010-08-25 18:59:06 UTC (rev 22442)
Changed blocks: 2, Lines Added: 14, Lines Deleted: 16; 2796 bytes

@@ -24,18 +24,16 @@
   </indexterm>
 
   <para>
-    The
-    <ulink url="http://dev.mysql.com/doc/refman/5.1/en/information-schema.html">
-    &INFORMATION_SCHEMA;</ulink> is a MySQL feature that helps you
-    monitor server activity to diagnose capacity and performance issues.
-    Several InnoDB-related &INFORMATION_SCHEMA; tables (&INNODB_CMP;,
-    &INNODB_CMP_RESET;, &INNODB_CMPMEM;, &INNODB_CMPMEM_RESET;,
-    &INNODB_TRX;, &INNODB_LOCKS; and &INNODB_LOCK_WAITS;) contain live
-    information about compressed &innodb; tables, the compressed
-    &innodb; buffer pool, all transactions currently executing inside
-    &innodb;, the locks that transactions hold and those that are
-    blocking transactions waiting for access to a resource (a table or
-    row).
+    The <link linkend="information-schema">&INFORMATION_SCHEMA;</link>
+    is a MySQL feature that helps you monitor server activity to
+    diagnose capacity and performance issues. Several InnoDB-related
+    &INFORMATION_SCHEMA; tables (&INNODB_CMP;, &INNODB_CMP_RESET;,
+    &INNODB_CMPMEM;, &INNODB_CMPMEM_RESET;, &INNODB_TRX;, &INNODB_LOCKS;
+    and &INNODB_LOCK_WAITS;) contain live information about compressed
+    &innodb; tables, the compressed &innodb; buffer pool, all
+    transactions currently executing inside &innodb;, the locks that
+    transactions hold and those that are blocking transactions waiting
+    for access to a resource (a table or row).
   </para>
 
 <!-- JDR: for 5.5 and up, not sure if this condition could ever be true -->

@@ -1526,10 +1524,10 @@
         glimpses at other, similarly fast-changing data, may not be in
         sync. Thus, you should be careful in comparing the data in the
         &innodb; transaction and locking tables with that in the
-        <ulink url='http://dev.mysql.com/doc/refman/5.1/en/processlist-table.html'>
-        &mysql; table &PROCESSLIST; </ulink>. The data from the
-        &PROCESSLIST; table does not come from the same snapshot as the
-        data about locking and transactions. Even if you issue a single
+        <link linkend='processlist-table'>&mysql; table
+        &PROCESSLIST;</link>. The data from the &PROCESSLIST; table does
+        not come from the same snapshot as the data about locking and
+        transactions. Even if you issue a single
         <literal>SELECT</literal> (<literal>JOIN</literal>ing
         &INNODB_TRX; and &PROCESSLIST;, for example), the content of
         those tables is generally not consistent. &INNODB_TRX; may


Modified: trunk/innodb-plugin-1.1/innodb-other-changes.xml
===================================================================
--- trunk/innodb-plugin-1.1/innodb-other-changes.xml	2010-08-25 18:34:36 UTC (rev 22441)
+++ trunk/innodb-plugin-1.1/innodb-other-changes.xml	2010-08-25 18:59:06 UTC (rev 22442)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 6; 913 bytes

@@ -233,12 +233,8 @@
         in an index key. A related parameter,
         &innodb_stats_on_metadata;, has existed since &mysql; release
         5.1.17 to control whether or not &innodb; performs statistics
-        gathering when metadata statements are executed. See the MySQL
-        manual on
-        <ulink
-      url="http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html"
-      >&innodb;
-        Startup Options and System Variables</ulink> for details.
+        gathering when metadata statements are executed. See
+        <xref linkend="innodb-parameters"/> for details.
       </para>
 
       <para>


Modified: trunk/innodb-plugin-1.1/innodb-performance.xml
===================================================================
--- trunk/innodb-plugin-1.1/innodb-performance.xml	2010-08-25 18:34:36 UTC (rev 22441)
+++ trunk/innodb-plugin-1.1/innodb-performance.xml	2010-08-25 18:59:06 UTC (rev 22442)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 6; 1502 bytes

@@ -1398,12 +1398,12 @@
     <para>
       Starting with &innodb_plugin; 1.1 with MySQL 5.5, you can profile
       certain internal InnoDB operations using the MySQL
-      <ulink url="http://dev.mysql.com/doc/refman/5.5/en/performance-schema.html">Performance
-      Schema feature</ulink>. This type of tuning is primarily for
-      expert users, those who push the limits of MySQL performance, read
-      the MySQL source code, and evaluate optimization strategies to
-      overcome performance bottlenecks. DBAs can also use this feature
-      for capacity planning, to see whether their typical workload
+      <link linkend="performance-schema">Performance Schema
+      feature</link>. This type of tuning is primarily for expert users,
+      those who push the limits of MySQL performance, read the MySQL
+      source code, and evaluate optimization strategies to overcome
+      performance bottlenecks. DBAs can also use this feature for
+      capacity planning, to see whether their typical workload
       encounters any performance bottlenecks with a particular
       combination of CPU, RAM, and disk storage; and if so, to judge
       whether performance can be improved by increasing the capacity of


Modified: trunk/innodb-plugin-1.1/innodb-plugin-introduction.xml
===================================================================
--- trunk/innodb-plugin-1.1/innodb-plugin-introduction.xml	2010-08-25 18:34:36 UTC (rev 22441)
+++ trunk/innodb-plugin-1.1/innodb-plugin-introduction.xml	2010-08-25 18:59:06 UTC (rev 22442)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 6; 939 bytes

@@ -36,12 +36,7 @@
           Since 2001, MySQL AB has distributed the &innodb;
           transactional storage engine with its releases (both source
           and binary). This is the storage engine that you can read
-          about in a dedicated chapter in the MySQL documentation (in
-          particular, the
-          <ulink url="http://dev.mysql.com/doc/refman/5.1/en/innodb.html">MySQL
-          5.1 manual</ulink> and the
-          <ulink url="http://dev.mysql.com/doc/refman/5.5/en/innodb.html">MySQL
-          5.5 manual</ulink>).
+          about in <xref linkend="innodb"/>.
         </para>
       </listitem>
 


Modified: trunk/innodb-plugin-1.1/innodb-upgrading.xml
===================================================================
--- trunk/innodb-plugin-1.1/innodb-upgrading.xml	2010-08-25 18:34:36 UTC (rev 22441)
+++ trunk/innodb-plugin-1.1/innodb-upgrading.xml	2010-08-25 18:59:06 UTC (rev 22442)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 5; 696 bytes

@@ -69,11 +69,9 @@
 
 <programlisting>SET GLOBAL innodb_fast_shutdown=0;</programlisting>
 
-      For the details of the shutdown procedure, see the MySQL manual on
-      <ulink
-    url="http://dev.mysql.com/doc/refman/5.5/en/server-shutdown.html"
-    >The
-      Shutdown Process</ulink>.
+      For the details of the shutdown procedure, see
+      <xref
+    linkend="server-shutdown"/>.
     </para>
 
     <para>


Thread
svn commit - mysqldoc@docsrva: r22442 - trunk/innodb-plugin-1.1john.russell25 Aug