List:Commits« Previous MessageNext Message »
From:paul.dubois Date:December 7 2010 8:27pm
Subject:svn commit - mysqldoc@docsrva: r24306 - in trunk: . refman-5.5 refman-5.6
View as plain text  
Author: paul
Date: 2010-12-07 21:27:15 +0100 (Tue, 07 Dec 2010)
New Revision: 24306

Log:
 r34762@dhcp-215:  paul | 2010-12-07 14:26:57 -0500
 Lowercase some more performance_schema stuff
 (output of SHOW ENGINE PERFORMANCE_SCHEMA STATUS, see Bug#58798)


Modified:
   trunk/refman-5.5/performance-schema-core.xml
   trunk/refman-5.5/sql-syntax-server-administration.xml
   trunk/refman-5.6/performance-schema-core.xml
   trunk/refman-5.6/sql-syntax-server-administration.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:45180
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:66486
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:45180
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:66486
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
ebeeeee4-b232-4669-a521-231442eced53:/mysqldoc-local/mysqldoc/trunk:34762


Modified: trunk/refman-5.5/performance-schema-core.xml
===================================================================
--- trunk/refman-5.5/performance-schema-core.xml	2010-12-07 20:18:11 UTC (rev 24305)
+++ trunk/refman-5.5/performance-schema-core.xml	2010-12-07 20:27:15 UTC (rev 24306)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 512 bytes

@@ -1841,7 +1841,7 @@
 ...
 *************************** 57. row ***************************
   Type: performance_schema
-  Name: PERFORMANCE_SCHEMA.MEMORY
+  Name: performance_schema.MEMORY
 Status: 26459600
 ...
 </programlisting>


Modified: trunk/refman-5.5/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.5/sql-syntax-server-administration.xml	2010-12-07 20:18:11 UTC (rev 24305)
+++ trunk/refman-5.5/sql-syntax-server-administration.xml	2010-12-07 20:27:15 UTC (rev 24306)
Changed blocks: 6, Lines Added: 19, Lines Deleted: 19; 4631 bytes

@@ -5825,20 +5825,20 @@
 ...
 *************************** 3. row ***************************
   Type: performance_schema
-  Name: events_waits_history.ROW_SIZE
+  Name: events_waits_history.row_size
 Status: 76
 *************************** 4. row ***************************
   Type: performance_schema
-  Name: events_waits_history.ROW_COUNT
+  Name: events_waits_history.row_count
 Status: 10000
 *************************** 5. row ***************************
   Type: performance_schema
-  Name: events_waits_history.MEMORY
+  Name: events_waits_history.memory
 Status: 760000
 ...
 *************************** 57. row ***************************
   Type: performance_schema
-  Name: PERFORMANCE_SCHEMA.MEMORY
+  Name: performance_schema.memory
 Status: 26459600
 ...
 </programlisting>

@@ -5860,8 +5860,8 @@
             Internal buffers that are exposed as a table in the
             <literal>performance_schema</literal> are named after the
             table. Examples:
-            <literal>events_waits_history.ROW_SIZE</literal>,
-            <literal>mutex_instances.ROW_COUNT</literal>.
+            <literal>events_waits_history.row_size</literal>,
+            <literal>mutex_instances.row_count</literal>.
           </para>
         </listitem>
 

@@ -5869,16 +5869,16 @@
           <para>
             Internal buffers that are not exposed as a table are named
             within parentheses. Examples:
-            <literal>(PFS_COND_CLASS).ROW_SIZE</literal>,
-            <literal>(PFS_MUTEX_CLASS).MEMORY</literal>.
+            <literal>(pfs_cond_class).row_size</literal>,
+            <literal>(pfs_mutex_class).memory</literal>.
           </para>
         </listitem>
 
         <listitem>
           <para>
             Values that apply to Performance Schema as a whole begin
-            with <literal>PERFORMANCE_SCHEMA</literal>. Example:
-            <literal>PERFORMANCE_SCHEMA.MEMORY</literal>.
+            with <literal>performance_schema</literal>. Example:
+            <literal>performance_schema.memory</literal>.
           </para>
         </listitem>
 

@@ -5892,14 +5892,14 @@
 
         <listitem>
           <para>
-            <literal>ROW_SIZE</literal> cannot be changed. It is the
+            <literal>row_size</literal> cannot be changed. It is the
             size of the internal record used by the implementation.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            <literal>ROW_COUNT</literal> can be changed depending on the
+            <literal>row_count</literal> can be changed depending on the
             configuration options.
           </para>
         </listitem>

@@ -5907,12 +5907,12 @@
         <listitem>
           <para>
             For a table,
-            <literal><replaceable>tbl_name</replaceable>.MEMORY</literal>
-            is the product of <literal>ROW_SIZE</literal> multiplied by
-            <literal>ROW_COUNT</literal>. For Performance Schema as a
-            whole, <literal>PERFORMANCE_SCHEMA.MEMORY</literal> is the
+            <literal><replaceable>tbl_name</replaceable>.memory</literal>
+            is the product of <literal>row_size</literal> multiplied by
+            <literal>row_count</literal>. For Performance Schema as a
+            whole, <literal>performance_schema.memory</literal> is the
             sum of all the memory used (the sum of all other
-            <literal>MEMORY</literal> values).
+            <literal>memory</literal> values).
           </para>
         </listitem>
 

@@ -5922,11 +5922,11 @@
         In some cases, there is a direct relationship between a
         configuration parameter and a <literal>SHOW ENGINE</literal>
         value. For example,
-        <literal>events_waits_history_long.ROW_COUNT</literal>
+        <literal>events_waits_history_long.row_count</literal>
         corresponds to
         <literal role="sysvar">performance_schema_events_waits_history_long_size</literal>.
         In other cases, the relationship is more complex. For example,
-        <literal>events_waits_history.ROW_COUNT</literal> corresponds to
+        <literal>events_waits_history.row_count</literal> corresponds to
         <literal role="sysvar">performance_schema_events_waits_history_size</literal>
         (the number of rows per thread) multiplied by
         <literal role="sysvar">performance_schema_max_thread_instances</literal>


Modified: trunk/refman-5.6/performance-schema-core.xml
===================================================================
--- trunk/refman-5.6/performance-schema-core.xml	2010-12-07 20:18:11 UTC (rev 24305)
+++ trunk/refman-5.6/performance-schema-core.xml	2010-12-07 20:27:15 UTC (rev 24306)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 512 bytes

@@ -1844,7 +1844,7 @@
 ...
 *************************** 57. row ***************************
   Type: performance_schema
-  Name: PERFORMANCE_SCHEMA.MEMORY
+  Name: performance_schema.MEMORY
 Status: 26459600
 ...
 </programlisting>


Modified: trunk/refman-5.6/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.6/sql-syntax-server-administration.xml	2010-12-07 20:18:11 UTC (rev 24305)
+++ trunk/refman-5.6/sql-syntax-server-administration.xml	2010-12-07 20:27:15 UTC (rev 24306)
Changed blocks: 6, Lines Added: 19, Lines Deleted: 19; 4631 bytes

@@ -5819,20 +5819,20 @@
 ...
 *************************** 3. row ***************************
   Type: performance_schema
-  Name: events_waits_history.ROW_SIZE
+  Name: events_waits_history.row_size
 Status: 76
 *************************** 4. row ***************************
   Type: performance_schema
-  Name: events_waits_history.ROW_COUNT
+  Name: events_waits_history.row_count
 Status: 10000
 *************************** 5. row ***************************
   Type: performance_schema
-  Name: events_waits_history.MEMORY
+  Name: events_waits_history.memory
 Status: 760000
 ...
 *************************** 57. row ***************************
   Type: performance_schema
-  Name: PERFORMANCE_SCHEMA.MEMORY
+  Name: performance_schema.memory
 Status: 26459600
 ...
 </programlisting>

@@ -5854,8 +5854,8 @@
             Internal buffers that are exposed as a table in the
             <literal>performance_schema</literal> are named after the
             table. Examples:
-            <literal>events_waits_history.ROW_SIZE</literal>,
-            <literal>mutex_instances.ROW_COUNT</literal>.
+            <literal>events_waits_history.row_size</literal>,
+            <literal>mutex_instances.row_count</literal>.
           </para>
         </listitem>
 

@@ -5863,16 +5863,16 @@
           <para>
             Internal buffers that are not exposed as a table are named
             within parentheses. Examples:
-            <literal>(PFS_COND_CLASS).ROW_SIZE</literal>,
-            <literal>(PFS_MUTEX_CLASS).MEMORY</literal>.
+            <literal>(pfs_cond_class).row_size</literal>,
+            <literal>(pfs_mutex_class).memory</literal>.
           </para>
         </listitem>
 
         <listitem>
           <para>
             Values that apply to Performance Schema as a whole begin
-            with <literal>PERFORMANCE_SCHEMA</literal>. Example:
-            <literal>PERFORMANCE_SCHEMA.MEMORY</literal>.
+            with <literal>performance_schema</literal>. Example:
+            <literal>performance_schema.memory</literal>.
           </para>
         </listitem>
 

@@ -5886,14 +5886,14 @@
 
         <listitem>
           <para>
-            <literal>ROW_SIZE</literal> cannot be changed. It is the
+            <literal>row_size</literal> cannot be changed. It is the
             size of the internal record used by the implementation.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            <literal>ROW_COUNT</literal> can be changed depending on the
+            <literal>row_count</literal> can be changed depending on the
             configuration options.
           </para>
         </listitem>

@@ -5901,12 +5901,12 @@
         <listitem>
           <para>
             For a table,
-            <literal><replaceable>tbl_name</replaceable>.MEMORY</literal>
-            is the product of <literal>ROW_SIZE</literal> multiplied by
-            <literal>ROW_COUNT</literal>. For Performance Schema as a
-            whole, <literal>PERFORMANCE_SCHEMA.MEMORY</literal> is the
+            <literal><replaceable>tbl_name</replaceable>.memory</literal>
+            is the product of <literal>row_size</literal> multiplied by
+            <literal>row_count</literal>. For Performance Schema as a
+            whole, <literal>performance_schema.memory</literal> is the
             sum of all the memory used (the sum of all other
-            <literal>MEMORY</literal> values).
+            <literal>memory</literal> values).
           </para>
         </listitem>
 

@@ -5916,11 +5916,11 @@
         In some cases, there is a direct relationship between a
         configuration parameter and a <literal>SHOW ENGINE</literal>
         value. For example,
-        <literal>events_waits_history_long.ROW_COUNT</literal>
+        <literal>events_waits_history_long.row_count</literal>
         corresponds to
         <literal role="sysvar">performance_schema_events_waits_history_long_size</literal>.
         In other cases, the relationship is more complex. For example,
-        <literal>events_waits_history.ROW_COUNT</literal> corresponds to
+        <literal>events_waits_history.row_count</literal> corresponds to
         <literal role="sysvar">performance_schema_events_waits_history_size</literal>
         (the number of rows per thread) multiplied by
         <literal role="sysvar">performance_schema_max_thread_instances</literal>


Thread
svn commit - mysqldoc@docsrva: r24306 - in trunk: . refman-5.5 refman-5.6paul.dubois7 Dec