| List: | Commits | « Previous MessageNext Message » | |
| From: | paul.dubois | Date: | April 9 2009 10:32pm |
| Subject: | svn commit - mysqldoc@docsrva: r14576 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-6.0 | ||
| View as plain text | |||
Author: paul Date: 2009-04-09 22:32:47 +0200 (Thu, 09 Apr 2009) New Revision: 14576 Log: r40360@frost: paul | 2009-04-09 15:30:52 -0500 Miscellaneous InnoDB revisions Modified: trunk/refman-4.1/se-innodb-core.xml trunk/refman-5.0/se-innodb-core.xml trunk/refman-5.1/se-innodb-core.xml trunk/refman-6.0/monitors-tmp.xml trunk/refman-6.0/se-innodb-core.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:41755 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:40358 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:37553 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:41755 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:40360 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:37553 Modified: trunk/refman-4.1/se-innodb-core.xml =================================================================== --- trunk/refman-4.1/se-innodb-core.xml 2009-04-09 20:20:16 UTC (rev 14575) +++ trunk/refman-4.1/se-innodb-core.xml 2009-04-09 20:32:47 UTC (rev 14576) Changed blocks: 3, Lines Added: 35, Lines Deleted: 14; 2998 bytes @@ -6036,14 +6036,24 @@ <para> The tablespace consists of database pages with a default size of - 16KB. The pages are grouped into extents of 64 consecutive - pages. The <quote>files</quote> inside a tablespace are called - <firstterm>segments</firstterm> in <literal>InnoDB</literal>. - The term <quote>rollback segment</quote> is somewhat confusing - because it actually contains many tablespace segments. + 16KB. The pages are grouped into extents of size 1MB (64 + consecutive pages). The <quote>files</quote> inside a tablespace + are called <firstterm>segments</firstterm> in + <literal>InnoDB</literal>. The term <quote>rollback + segment</quote> is somewhat confusing because it actually + contains many tablespace segments. </para> <para> + When a segment grows inside the tablespace, + <literal>InnoDB</literal> allocates the first 32 pages to it + individually. After that, <literal>InnoDB</literal> starts to + allocate whole extents to the segment. <literal>InnoDB</literal> + can add up to 4 extents at a time to a large segment to ensure + good sequentiality of data. + </para> + + <para> Two segments are allocated for each index in <literal>InnoDB</literal>. One is for non-leaf nodes of the B-tree, the other is for the leaf nodes. The idea here is to @@ -6052,15 +6062,6 @@ </para> <para> - When a segment grows inside the tablespace, - <literal>InnoDB</literal> allocates the first 32 pages to it - individually. After that, <literal>InnoDB</literal> starts to - allocate whole extents to the segment. <literal>InnoDB</literal> - can add to a large segment up to 4 extents at a time to ensure - good sequentiality of data. - </para> - - <para> Some pages in the tablespace contain bitmaps of other pages, and therefore a few extents in an <literal>InnoDB</literal> tablespace cannot be allocated to segments as a whole, but only @@ -6090,6 +6091,26 @@ <xref linkend="innodb-multi-versioning"/>.) </para> + <indexterm> + <primary>InnoDB</primary> + <secondary>Monitors</secondary> + </indexterm> + + <indexterm> + <primary>Monitors</primary> + <secondary>InnoDB</secondary> + </indexterm> + + <indexterm> + <primary>Tablespace Monitor</primary> + <secondary>InnoDB</secondary> + </indexterm> + + <para> + To see information about the tablespace, use the Tablespace + Monitor. See <xref linkend="innodb-monitors"/>. + </para> + </section> <section id="innodb-file-defragmenting"> Modified: trunk/refman-5.0/se-innodb-core.xml =================================================================== --- trunk/refman-5.0/se-innodb-core.xml 2009-04-09 20:20:16 UTC (rev 14575) +++ trunk/refman-5.0/se-innodb-core.xml 2009-04-09 20:32:47 UTC (rev 14576) Changed blocks: 3, Lines Added: 35, Lines Deleted: 14; 2998 bytes @@ -6243,14 +6243,24 @@ <para> The tablespace consists of database pages with a default size of - 16KB. The pages are grouped into extents of 64 consecutive - pages. The <quote>files</quote> inside a tablespace are called - <firstterm>segments</firstterm> in <literal>InnoDB</literal>. - The term <quote>rollback segment</quote> is somewhat confusing - because it actually contains many tablespace segments. + 16KB. The pages are grouped into extents of size 1MB (64 + consecutive pages). The <quote>files</quote> inside a tablespace + are called <firstterm>segments</firstterm> in + <literal>InnoDB</literal>. The term <quote>rollback + segment</quote> is somewhat confusing because it actually + contains many tablespace segments. </para> <para> + When a segment grows inside the tablespace, + <literal>InnoDB</literal> allocates the first 32 pages to it + individually. After that, <literal>InnoDB</literal> starts to + allocate whole extents to the segment. <literal>InnoDB</literal> + can add up to 4 extents at a time to a large segment to ensure + good sequentiality of data. + </para> + + <para> Two segments are allocated for each index in <literal>InnoDB</literal>. One is for non-leaf nodes of the B-tree, the other is for the leaf nodes. The idea here is to @@ -6259,15 +6269,6 @@ </para> <para> - When a segment grows inside the tablespace, - <literal>InnoDB</literal> allocates the first 32 pages to it - individually. After that, <literal>InnoDB</literal> starts to - allocate whole extents to the segment. <literal>InnoDB</literal> - can add to a large segment up to 4 extents at a time to ensure - good sequentiality of data. - </para> - - <para> Some pages in the tablespace contain bitmaps of other pages, and therefore a few extents in an <literal>InnoDB</literal> tablespace cannot be allocated to segments as a whole, but only @@ -6297,6 +6298,26 @@ <xref linkend="innodb-multi-versioning"/>.) </para> + <indexterm> + <primary>InnoDB</primary> + <secondary>Monitors</secondary> + </indexterm> + + <indexterm> + <primary>Monitors</primary> + <secondary>InnoDB</secondary> + </indexterm> + + <indexterm> + <primary>Tablespace Monitor</primary> + <secondary>InnoDB</secondary> + </indexterm> + + <para> + To see information about the tablespace, use the Tablespace + Monitor. See <xref linkend="innodb-monitors"/>. + </para> + </section> <section id="innodb-file-defragmenting"> Modified: trunk/refman-5.1/se-innodb-core.xml =================================================================== --- trunk/refman-5.1/se-innodb-core.xml 2009-04-09 20:20:16 UTC (rev 14575) +++ trunk/refman-5.1/se-innodb-core.xml 2009-04-09 20:32:47 UTC (rev 14576) Changed blocks: 3, Lines Added: 35, Lines Deleted: 14; 2998 bytes @@ -7079,14 +7079,24 @@ <para> The tablespace consists of database pages with a default size of - 16KB. The pages are grouped into extents of 64 consecutive - pages. The <quote>files</quote> inside a tablespace are called - <firstterm>segments</firstterm> in <literal>InnoDB</literal>. - The term <quote>rollback segment</quote> is somewhat confusing - because it actually contains many tablespace segments. + 16KB. The pages are grouped into extents of size 1MB (64 + consecutive pages). The <quote>files</quote> inside a tablespace + are called <firstterm>segments</firstterm> in + <literal>InnoDB</literal>. The term <quote>rollback + segment</quote> is somewhat confusing because it actually + contains many tablespace segments. </para> <para> + When a segment grows inside the tablespace, + <literal>InnoDB</literal> allocates the first 32 pages to it + individually. After that, <literal>InnoDB</literal> starts to + allocate whole extents to the segment. <literal>InnoDB</literal> + can add up to 4 extents at a time to a large segment to ensure + good sequentiality of data. + </para> + + <para> Two segments are allocated for each index in <literal>InnoDB</literal>. One is for non-leaf nodes of the B-tree, the other is for the leaf nodes. The idea here is to @@ -7095,15 +7105,6 @@ </para> <para> - When a segment grows inside the tablespace, - <literal>InnoDB</literal> allocates the first 32 pages to it - individually. After that, <literal>InnoDB</literal> starts to - allocate whole extents to the segment. <literal>InnoDB</literal> - can add to a large segment up to 4 extents at a time to ensure - good sequentiality of data. - </para> - - <para> Some pages in the tablespace contain bitmaps of other pages, and therefore a few extents in an <literal>InnoDB</literal> tablespace cannot be allocated to segments as a whole, but only @@ -7133,6 +7134,26 @@ <xref linkend="innodb-multi-versioning"/>.) </para> + <indexterm> + <primary>InnoDB</primary> + <secondary>Monitors</secondary> + </indexterm> + + <indexterm> + <primary>Monitors</primary> + <secondary>InnoDB</secondary> + </indexterm> + + <indexterm> + <primary>Tablespace Monitor</primary> + <secondary>InnoDB</secondary> + </indexterm> + + <para> + To see information about the tablespace, use the Tablespace + Monitor. See <xref linkend="innodb-monitors"/>. + </para> + </section> <section id="innodb-file-defragmenting"> Modified: trunk/refman-6.0/monitors-tmp.xml =================================================================== --- trunk/refman-6.0/monitors-tmp.xml 2009-04-09 20:20:16 UTC (rev 14575) +++ trunk/refman-6.0/monitors-tmp.xml 2009-04-09 20:32:47 UTC (rev 14576) Changed blocks: 5, Lines Added: 18, Lines Deleted: 19; 2852 bytes @@ -142,17 +142,14 @@ </programlisting> <para> - [Look for segment where used < res] - </para> - - <para> The output includes information about the tablespace as a whole, followed by a breakdown for each segment within the tablespace. </para> <para> - A page in <literal>InnoDB</literal> is 16KB. And extent is 1MB (16 - pages). + The tablespace consists of database pages with a default size of + 16KB. The pages are grouped into extents of size 1MB (64 + consecutive pages). </para> <para> @@ -207,13 +204,6 @@ </para> <para> - The tablespace is divided into 64-page extents. When a segment - grows, it starts at a single page, and <literal>InnoDB</literal> - allocates the first 32 pages for it individually. After that, - <literal>InnoDB</literal> allocates complete 64-page extents. - </para> - - <para> <literal>free extents</literal>: The number of extents allocated for the segment that are completely unused. </para> @@ -229,11 +219,14 @@ </para> <para> - A segment is allocated a page at a time as it grows, up to 32 - pages (this is the <literal>fragm pages</literal> value). After - that, the segment grows by an extent (16 pages) at a time. For the - example segment, it has 32 fragment pages, plus 2 extents (64 - pages each), for a total of 160 pages. + When a segment grows, it starts as a single page, and + <literal>InnoDB</literal> allocates the first pages for it + individually, up to 32 pages (this is the <literal>fragm + pages</literal> value). After that, <literal>InnoDB</literal> + allocates complete 64-page extents. <literal>InnoDB</literal> can + add up to 4 extents at a time to a large segment to ensure good + sequentiality of data. For the example segment, it has 32 fragment + pages, plus 2 extents (64 pages each), for a total of 160 pages. </para> </section> @@ -252,6 +245,10 @@ (reformatted slightly): </para> + <para> + [THIS NEEDS TO BE VERSION SPECIFIC] + </para> + <programlisting> =========================================== 090408 21:27:53 INNODB TABLE MONITOR OUTPUT @@ -406,7 +403,9 @@ <para> <literal>GEN_CLUST_INDEX</literal>: This indicates that the index is the clustered index that is created automatically if the table - definition doesn't include a primary key? + definition doesn't include a primary key or + non-<literal>NULL</literal> unique index. See + <xref linkend="innodb-index-types"/>. </para> <para> Modified: trunk/refman-6.0/se-innodb-core.xml =================================================================== --- trunk/refman-6.0/se-innodb-core.xml 2009-04-09 20:20:16 UTC (rev 14575) +++ trunk/refman-6.0/se-innodb-core.xml 2009-04-09 20:32:47 UTC (rev 14576) Changed blocks: 3, Lines Added: 35, Lines Deleted: 14; 2998 bytes @@ -6868,14 +6868,24 @@ <para> The tablespace consists of database pages with a default size of - 16KB. The pages are grouped into extents of 64 consecutive - pages. The <quote>files</quote> inside a tablespace are called - <firstterm>segments</firstterm> in <literal>InnoDB</literal>. - The term <quote>rollback segment</quote> is somewhat confusing - because it actually contains many tablespace segments. + 16KB. The pages are grouped into extents of size 1MB (64 + consecutive pages). The <quote>files</quote> inside a tablespace + are called <firstterm>segments</firstterm> in + <literal>InnoDB</literal>. The term <quote>rollback + segment</quote> is somewhat confusing because it actually + contains many tablespace segments. </para> <para> + When a segment grows inside the tablespace, + <literal>InnoDB</literal> allocates the first 32 pages to it + individually. After that, <literal>InnoDB</literal> starts to + allocate whole extents to the segment. <literal>InnoDB</literal> + can add up to 4 extents at a time to a large segment to ensure + good sequentiality of data. + </para> + + <para> Two segments are allocated for each index in <literal>InnoDB</literal>. One is for non-leaf nodes of the B-tree, the other is for the leaf nodes. The idea here is to @@ -6884,15 +6894,6 @@ </para> <para> - When a segment grows inside the tablespace, - <literal>InnoDB</literal> allocates the first 32 pages to it - individually. After that, <literal>InnoDB</literal> starts to - allocate whole extents to the segment. <literal>InnoDB</literal> - can add to a large segment up to 4 extents at a time to ensure - good sequentiality of data. - </para> - - <para> Some pages in the tablespace contain bitmaps of other pages, and therefore a few extents in an <literal>InnoDB</literal> tablespace cannot be allocated to segments as a whole, but only @@ -6922,6 +6923,26 @@ <xref linkend="innodb-multi-versioning"/>.) </para> + <indexterm> + <primary>InnoDB</primary> + <secondary>Monitors</secondary> + </indexterm> + + <indexterm> + <primary>Monitors</primary> + <secondary>InnoDB</secondary> + </indexterm> + + <indexterm> + <primary>Tablespace Monitor</primary> + <secondary>InnoDB</secondary> + </indexterm> + + <para> + To see information about the tablespace, use the Tablespace + Monitor. See <xref linkend="innodb-monitors"/>. + </para> + </section> <section id="innodb-file-defragmenting">
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r14576 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul.dubois | 9 Apr 2009 |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.505 sec. using MySQL 5.1.14-beta-log