diff --git a/product/en/docs-mogdb/v1.1/administrator-guide/routine-maintenance.md b/product/en/docs-mogdb/v1.1/administrator-guide/routine-maintenance.md index 6b7119a014317b8d5f2ee4efb76b49e3447434e5..1f4c866a56436c04b0f55f7d8f2de76db5f5746d 100644 --- a/product/en/docs-mogdb/v1.1/administrator-guide/routine-maintenance.md +++ b/product/en/docs-mogdb/v1.1/administrator-guide/routine-maintenance.md @@ -1427,7 +1427,7 @@ When data deletion is repeatedly performed in the database, index keys will be d The database supports B-tree indexes. Recreating a B-tree index routinely helps improve query efficiency. -- If a large amount of data is deleted, index keys on the index pages will be deleted. As a result, the number of index pages reduces and index bloat occurs. Recreating an index helps reclaim wasted space. +- If a large amount of data is deleted, index keys on the index pages will be deleted. But index pages will not be directly deleted, that is the number of index pages will not decrease, then index bloat occurs. Recreating an index helps reclaim wasted space. - In a newly created index, pages with adjacent logical structures tend to have adjacent physical structures. Therefore, a new index achieves a higher access speed than an index that has been updated for multiple times. **Methods** diff --git a/product/en/docs-mogdb/v1.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/en/docs-mogdb/v1.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index cfa38546f63ac7c8e1dd8d508e74e86c15c59190..0ed746aa2670f73318fe8fb3a9059776e1a06aa2 100644 --- a/product/en/docs-mogdb/v1.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/en/docs-mogdb/v1.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ When data deletion is repeatedly performed in the database, index keys will be d The database supports B-tree indexes. Recreating a B-tree index routinely helps improve query efficiency. -- If a large amount of data is deleted, index keys on the index pages will be deleted. As a result, the number of index pages reduces and index bloat occurs. Recreating an index helps reclaim wasted space. +- If a large amount of data is deleted, index keys on the index pages will be deleted. But index pages will not be directly deleted, that is the number of index pages will not decrease, then index bloat occurs. Recreating an index helps reclaim wasted space. - In a newly created index, pages with adjacent logical structures tend to have adjacent physical structures. Therefore, a new index achieves a higher access speed than an index that has been updated for multiple times. **Methods** diff --git a/product/en/docs-mogdb/v2.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/en/docs-mogdb/v2.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index cfa38546f63ac7c8e1dd8d508e74e86c15c59190..0ed746aa2670f73318fe8fb3a9059776e1a06aa2 100644 --- a/product/en/docs-mogdb/v2.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/en/docs-mogdb/v2.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ When data deletion is repeatedly performed in the database, index keys will be d The database supports B-tree indexes. Recreating a B-tree index routinely helps improve query efficiency. -- If a large amount of data is deleted, index keys on the index pages will be deleted. As a result, the number of index pages reduces and index bloat occurs. Recreating an index helps reclaim wasted space. +- If a large amount of data is deleted, index keys on the index pages will be deleted. But index pages will not be directly deleted, that is the number of index pages will not decrease, then index bloat occurs. Recreating an index helps reclaim wasted space. - In a newly created index, pages with adjacent logical structures tend to have adjacent physical structures. Therefore, a new index achieves a higher access speed than an index that has been updated for multiple times. **Methods** diff --git a/product/en/docs-mogdb/v2.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/en/docs-mogdb/v2.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index cfa38546f63ac7c8e1dd8d508e74e86c15c59190..0ed746aa2670f73318fe8fb3a9059776e1a06aa2 100644 --- a/product/en/docs-mogdb/v2.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/en/docs-mogdb/v2.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ When data deletion is repeatedly performed in the database, index keys will be d The database supports B-tree indexes. Recreating a B-tree index routinely helps improve query efficiency. -- If a large amount of data is deleted, index keys on the index pages will be deleted. As a result, the number of index pages reduces and index bloat occurs. Recreating an index helps reclaim wasted space. +- If a large amount of data is deleted, index keys on the index pages will be deleted. But index pages will not be directly deleted, that is the number of index pages will not decrease, then index bloat occurs. Recreating an index helps reclaim wasted space. - In a newly created index, pages with adjacent logical structures tend to have adjacent physical structures. Therefore, a new index achieves a higher access speed than an index that has been updated for multiple times. **Methods** diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index 0a8c2b31941943f233f3e4f397ce12790613e460..c569257883ecda60ec5bddcaaff516d4f06466bb 100644 --- a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ When data deletion is repeatedly performed in the database, index keys will be d The database supports B-tree indexes. Recreating a B-tree index routinely helps improve query efficiency. -- If a large amount of data is deleted, index keys on the index pages will be deleted. As a result, the number of index pages reduces and index bloat occurs. Recreating an index helps reclaim wasted space. +- If a large amount of data is deleted, index keys on the index pages will be deleted. But index pages will not be directly deleted, that is the number of index pages will not decrease, then index bloat occurs. Recreating an index helps reclaim wasted space. - In a newly created index, pages with adjacent logical structures tend to have adjacent physical structures. Therefore, a new index achieves a higher access speed than an index that has been updated for multiple times. **Methods** diff --git a/product/en/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md b/product/en/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md index 88c2a35199887c57710c6a318496eb6a3fc88c58..345fa28401cf3295cffa738a2bb09f8a1728dc6a 100644 --- a/product/en/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md +++ b/product/en/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md @@ -44,7 +44,6 @@ The following table describes the minimum hardware requirements of MogDB. When p | Oracle Linux 8 (x86_64) | √ | | √ | | Red Hat Enterprise Linux 7 (x86_64) | √ | √ | √ | | Red Hat Enterprise Linux 8 (x86_64) | √ | | √ | -| Rocky Linux 7 (x86_64) | √ | | √ | | Rocky Linux 8 (x86_64) | √ | | √ | | SLES 12 (arm64) | √ | | √ | | UOS 20 (arm64) | √ | √ | √ | diff --git a/product/en/docs-mogdb/v3.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/en/docs-mogdb/v3.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index ac7b37b20dffc0ef1e2d0c65c96aa440b5b1cd14..6bfacf4c30f290af515c7b353724c58a6c942a8f 100644 --- a/product/en/docs-mogdb/v3.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/en/docs-mogdb/v3.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ When data deletion is repeatedly performed in the database, index keys will be d The database supports B-tree indexes. Recreating a B-tree index routinely helps improve query efficiency. -- If a large amount of data is deleted, index keys on the index pages will be deleted. As a result, the number of index pages reduces and index bloat occurs. Recreating an index helps reclaim wasted space. +- If a large amount of data is deleted, index keys on the index pages will be deleted. But index pages will not be directly deleted, that is the number of index pages will not decrease, then index bloat occurs. Recreating an index helps reclaim wasted space. - In a newly created index, pages with adjacent logical structures tend to have adjacent physical structures. Therefore, a new index achieves a higher access speed than an index that has been updated for multiple times. **Methods** diff --git a/product/en/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md b/product/en/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md index dece2883c1cf5c90a563a9a9c7c44b7248b4ef10..41b026b0962879b6a7387069c61cdb5b093013c6 100644 --- a/product/en/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md +++ b/product/en/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md @@ -43,7 +43,6 @@ The following table describes the minimum hardware requirements of MogDB. When p | Oracle Linux 8 (x86_64) | √ | | √ | | Red Hat Enterprise Linux 7 (x86_64) | √ | √ | √ | | Red Hat Enterprise Linux 8 (x86_64) | √ | | √ | -| Rocky Linux 7 (x86_64) | √ | | √ | | Rocky Linux 8 (x86_64) | √ | | √ | | SLES 12 (arm64) | √ | | √ | | UOS 20 (arm64) | √ | √ | √ | diff --git a/product/en/docs-mogdb/v3.1/quick-start/installation-on-a-single-node.md b/product/en/docs-mogdb/v3.1/quick-start/installation-on-a-single-node.md index 2e0be8fddc2bb01ed0ef600c244adb289beeabce..d13628eaaaf7c7f624048b8552cc0a923b0bc3e1 100644 --- a/product/en/docs-mogdb/v3.1/quick-start/installation-on-a-single-node.md +++ b/product/en/docs-mogdb/v3.1/quick-start/installation-on-a-single-node.md @@ -28,8 +28,7 @@ You can run the following command to check operating systems where MogDB can be | Oracle Linux 7 (x86_64) | Oracle Linux 8 (x86_64) | Red Hat Enterprise Linux 7 (x86_64) - | Red Hat Enterprise Linux 8 (x86_64) - | Rocky Linux 7 (x86_64) + | Red Hat Enterprise Linux 8 (x86_64) | Rocky Linux 8 (x86_64) | SLES 12 (arm64) | UOS 20 (arm64) diff --git a/product/en/docs-mogdb/v5.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/en/docs-mogdb/v5.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index 8547ce89bbe2a0ed7a042bf0123a49267a3044c3..5ddb4d73e82c2d36667951015023863e5461aae7 100644 --- a/product/en/docs-mogdb/v5.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/en/docs-mogdb/v5.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ When data deletion is repeatedly performed in the database, index keys will be d The database supports B-tree indexes. Recreating a B-tree index routinely helps improve query efficiency. -- If a large amount of data is deleted, index keys on the index pages will be deleted. As a result, the number of index pages reduces and index bloat occurs. Recreating an index helps reclaim wasted space. +- If a large amount of data is deleted, index keys on the index pages will be deleted. But index pages will not be directly deleted, that is the number of index pages will not decrease, then index bloat occurs. Recreating an index helps reclaim wasted space. - In a newly created index, pages with adjacent logical structures tend to have adjacent physical structures. Therefore, a new index achieves a higher access speed than an index that has been updated for multiple times. **Methods** diff --git a/product/en/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md b/product/en/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md index 88c2a35199887c57710c6a318496eb6a3fc88c58..345fa28401cf3295cffa738a2bb09f8a1728dc6a 100644 --- a/product/en/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md +++ b/product/en/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md @@ -44,7 +44,6 @@ The following table describes the minimum hardware requirements of MogDB. When p | Oracle Linux 8 (x86_64) | √ | | √ | | Red Hat Enterprise Linux 7 (x86_64) | √ | √ | √ | | Red Hat Enterprise Linux 8 (x86_64) | √ | | √ | -| Rocky Linux 7 (x86_64) | √ | | √ | | Rocky Linux 8 (x86_64) | √ | | √ | | SLES 12 (arm64) | √ | | √ | | UOS 20 (arm64) | √ | √ | √ | diff --git a/product/en/docs-mogdb/v5.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/en/docs-mogdb/v5.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index 8547ce89bbe2a0ed7a042bf0123a49267a3044c3..5ddb4d73e82c2d36667951015023863e5461aae7 100644 --- a/product/en/docs-mogdb/v5.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/en/docs-mogdb/v5.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ When data deletion is repeatedly performed in the database, index keys will be d The database supports B-tree indexes. Recreating a B-tree index routinely helps improve query efficiency. -- If a large amount of data is deleted, index keys on the index pages will be deleted. As a result, the number of index pages reduces and index bloat occurs. Recreating an index helps reclaim wasted space. +- If a large amount of data is deleted, index keys on the index pages will be deleted. But index pages will not be directly deleted, that is the number of index pages will not decrease, then index bloat occurs. Recreating an index helps reclaim wasted space. - In a newly created index, pages with adjacent logical structures tend to have adjacent physical structures. Therefore, a new index achieves a higher access speed than an index that has been updated for multiple times. **Methods** diff --git a/product/en/docs-mogdb/v5.1/installation-guide/installation-preparation/environment-requirement.md b/product/en/docs-mogdb/v5.1/installation-guide/installation-preparation/environment-requirement.md index 88c2a35199887c57710c6a318496eb6a3fc88c58..345fa28401cf3295cffa738a2bb09f8a1728dc6a 100644 --- a/product/en/docs-mogdb/v5.1/installation-guide/installation-preparation/environment-requirement.md +++ b/product/en/docs-mogdb/v5.1/installation-guide/installation-preparation/environment-requirement.md @@ -44,7 +44,6 @@ The following table describes the minimum hardware requirements of MogDB. When p | Oracle Linux 8 (x86_64) | √ | | √ | | Red Hat Enterprise Linux 7 (x86_64) | √ | √ | √ | | Red Hat Enterprise Linux 8 (x86_64) | √ | | √ | -| Rocky Linux 7 (x86_64) | √ | | √ | | Rocky Linux 8 (x86_64) | √ | | √ | | SLES 12 (arm64) | √ | | √ | | UOS 20 (arm64) | √ | √ | √ | diff --git a/product/zh/docs-mogdb/v1.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/zh/docs-mogdb/v1.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index ed733d752c3d82355de3236687d0925ce5b0718e..b6da94ab1fa1e7d4649c8d5fc4dbdfc5c2b87553 100644 --- a/product/zh/docs-mogdb/v1.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/zh/docs-mogdb/v1.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ date: 2021-03-04 数据库支持的索引类型为B-tree索引，例行重建索引可有效的提高查询效率。 -- 如果数据发生大量删除后，索引页面上的索引键将被删除，导致索引页面数量的减少，造成索引膨胀。重建索引可回收浪费的空间。 +- 如果数据发生大量删除后，索引页面上的索引键将被删除，但索引页面并不会直接删除，即索引页面数量并不会减少，因此会造成索引膨胀。重建索引可回收浪费的空间。 - 新建的索引中逻辑结构相邻的页面，通常在物理结构中也是相邻的，所以一个新建的索引比更新了多次的索引访问速度要快。
diff --git a/product/zh/docs-mogdb/v2.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/zh/docs-mogdb/v2.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index ed733d752c3d82355de3236687d0925ce5b0718e..b6da94ab1fa1e7d4649c8d5fc4dbdfc5c2b87553 100644 --- a/product/zh/docs-mogdb/v2.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/zh/docs-mogdb/v2.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ date: 2021-03-04 数据库支持的索引类型为B-tree索引，例行重建索引可有效的提高查询效率。 -- 如果数据发生大量删除后，索引页面上的索引键将被删除，导致索引页面数量的减少，造成索引膨胀。重建索引可回收浪费的空间。 +- 如果数据发生大量删除后，索引页面上的索引键将被删除，但索引页面并不会直接删除，即索引页面数量并不会减少，因此会造成索引膨胀。重建索引可回收浪费的空间。 - 新建的索引中逻辑结构相邻的页面，通常在物理结构中也是相邻的，所以一个新建的索引比更新了多次的索引访问速度要快。
diff --git a/product/zh/docs-mogdb/v2.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/zh/docs-mogdb/v2.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index 2d8941ed0e58c756eda01bf7a5b24c742b8a53d6..e8d70ad5df0173c87bd62e8c2bb8ea648883669f 100644 --- a/product/zh/docs-mogdb/v2.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/zh/docs-mogdb/v2.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ date: 2021-03-04 数据库支持的索引类型为B-tree索引，例行重建索引可有效的提高查询效率。 -- 如果数据发生大量删除后，索引页面上的索引键将被删除，导致索引页面数量的减少，造成索引膨胀。重建索引可回收浪费的空间。 +- 如果数据发生大量删除后，索引页面上的索引键将被删除，但索引页面并不会直接删除，即索引页面数量并不会减少，因此会造成索引膨胀。重建索引可回收浪费的空间。 - 新建的索引中逻辑结构相邻的页面，通常在物理结构中也是相邻的，所以一个新建的索引比更新了多次的索引访问速度要快。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index 42e0e6262e506afb750a0d082aceb391b5410c8b..d1bc7d58c5e021d5354b60ef8047faeea2261582 100644 --- a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ date: 2021-03-04 数据库支持的索引类型为B-tree索引，例行重建索引可有效的提高查询效率。 -- 如果数据发生大量删除后，索引页面上的索引键将被删除，导致索引页面数量的减少，造成索引膨胀。重建索引可回收浪费的空间。 +- 如果数据发生大量删除后，索引页面上的索引键将被删除，但索引页面并不会直接删除，即索引页面数量并不会减少，因此会造成索引膨胀。重建索引可回收浪费的空间。 - 新建的索引中逻辑结构相邻的页面，通常在物理结构中也是相邻的，所以一个新建的索引比更新了多次的索引访问速度要快。
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md b/product/zh/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md index dccddc4e9709a2e8486a0b5a63cd1b9227aa1450..ade1326780611cc2f2d1789bd1815c3a2cbec39e 100644 --- a/product/zh/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md +++ b/product/zh/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md @@ -44,7 +44,6 @@ date: 2021-04-2 | Oracle Linux 8 (x86_64) | √ | | √ | | Red Hat Enterprise Linux 7 (x86_64) | √ | √ | √ | | Red Hat Enterprise Linux 8 (x86_64) | √ | | √ | -| Rocky Linux 7 (x86_64) | √ | | √ | | Rocky Linux 8 (x86_64) | √ | | √ | | SLES 12 (arm64) | √ | | √ | | UOS 20 (arm64) | √ | √ | √ | diff --git a/product/zh/docs-mogdb/v3.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/zh/docs-mogdb/v3.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index 52b903e4afa9e8b0539b8e91a29b15ca0c3d0fc5..f53c9cde793c28b12a199e3f1493ebf24e45b7b3 100644 --- a/product/zh/docs-mogdb/v3.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/zh/docs-mogdb/v3.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ date: 2021-03-04 数据库支持的索引类型为B-tree索引，例行重建索引可有效的提高查询效率。 -- 如果数据发生大量删除后，索引页面上的索引键将被删除，导致索引页面数量的减少，造成索引膨胀。重建索引可回收浪费的空间。 +- 如果数据发生大量删除后，索引页面上的索引键将被删除，但索引页面并不会直接删除，即索引页面数量并不会减少，因此会造成索引膨胀。重建索引可回收浪费的空间。 - 新建的索引中逻辑结构相邻的页面，通常在物理结构中也是相邻的，所以一个新建的索引比更新了多次的索引访问速度要快。
diff --git a/product/zh/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md b/product/zh/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md index 2cc61317fdaec54556e03a3a211c769e60a2a6fe..150c997de04d52ccf97cbfe66418d4b2f3ddb8d9 100644 --- a/product/zh/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md +++ b/product/zh/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md @@ -43,7 +43,6 @@ date: 2021-04-2 | Oracle Linux 8 (x86_64) | √ | √ | | Red Hat Enterprise Linux 7 (x86_64) | √ | √ | | Red Hat Enterprise Linux 8 (x86_64) | √ | √ | -| Rocky Linux 7 (x86_64) | √ | √ | | Rocky Linux 8 (x86_64) | √ | √ | | SLES 12 (arm64) | √ | √ | | UOS 20 (arm64) | √ | √ | diff --git a/product/zh/docs-mogdb/v3.1/quick-start/installation-on-a-single-node.md b/product/zh/docs-mogdb/v3.1/quick-start/installation-on-a-single-node.md index d6e69362f6f90351e943d919bd7e120e7fb124c7..b6d04df4a5413014c0dfce71c31427237c7c506b 100644 --- a/product/zh/docs-mogdb/v3.1/quick-start/installation-on-a-single-node.md +++ b/product/zh/docs-mogdb/v3.1/quick-start/installation-on-a-single-node.md @@ -28,8 +28,7 @@ PTK (Provisioning Toolkit)是一款针对 MogDB 数据库开发的软件安装 | Oracle Linux 7 (x86_64) | Oracle Linux 8 (x86_64) | Red Hat Enterprise Linux 7 (x86_64) - | Red Hat Enterprise Linux 8 (x86_64) - | Rocky Linux 7 (x86_64) + | Red Hat Enterprise Linux 8 (x86_64) | Rocky Linux 8 (x86_64) | SLES 12 (arm64) | UOS 20 (arm64) diff --git a/product/zh/docs-mogdb/v5.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/zh/docs-mogdb/v5.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index 52b903e4afa9e8b0539b8e91a29b15ca0c3d0fc5..f53c9cde793c28b12a199e3f1493ebf24e45b7b3 100644 --- a/product/zh/docs-mogdb/v5.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/zh/docs-mogdb/v5.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ date: 2021-03-04 数据库支持的索引类型为B-tree索引，例行重建索引可有效的提高查询效率。 -- 如果数据发生大量删除后，索引页面上的索引键将被删除，导致索引页面数量的减少，造成索引膨胀。重建索引可回收浪费的空间。 +- 如果数据发生大量删除后，索引页面上的索引键将被删除，但索引页面并不会直接删除，即索引页面数量并不会减少，因此会造成索引膨胀。重建索引可回收浪费的空间。 - 新建的索引中逻辑结构相邻的页面，通常在物理结构中也是相邻的，所以一个新建的索引比更新了多次的索引访问速度要快。
diff --git a/product/zh/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md b/product/zh/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md index 8843d7292d76a704a2af510651aeca031d729128..7068490b48023dfc341e83c6650ede0a67f299f3 100644 --- a/product/zh/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md +++ b/product/zh/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md @@ -44,7 +44,6 @@ date: 2021-04-2 | Oracle Linux 8 (x86_64) | √ | √ | | Red Hat Enterprise Linux 7 (x86_64) | √ | √ | | Red Hat Enterprise Linux 8 (x86_64) | √ | √ | -| Rocky Linux 7 (x86_64) | √ | √ | | Rocky Linux 8 (x86_64) | √ | √ | | SLES 12 (arm64) | √ | √ | | UOS 20 (arm64) | √ | √ | diff --git a/product/zh/docs-mogdb/v5.0/reference-guide/sql-reference/transaction/transaction-auto-commit.md b/product/zh/docs-mogdb/v5.0/reference-guide/sql-reference/transaction/transaction-auto-commit.md index c36467b739b600aa14f2596d1c4622bbc5c8492e..8550b071d2dfaeca3acd241ce891447066b4a74b 100644 --- a/product/zh/docs-mogdb/v5.0/reference-guide/sql-reference/transaction/transaction-auto-commit.md +++ b/product/zh/docs-mogdb/v5.0/reference-guide/sql-reference/transaction/transaction-auto-commit.md @@ -19,7 +19,7 @@ Oracle的事务状态控制与MogDB存在差异，Oracle对于只读命令不启 GUC参数[behavior_compat_options](../../guc-parameters/version-and-platform-compatibility/platform-and-client-compatibility.md#behavior_compat_options)新增配置项compat_oracle_txn_control。 -- 在驱动为非自动提交模式下，可通过以下方法开启此功能： +- 在驱动为非自动提交模式 (autocommit = off) 下，可通过以下方法开启此功能： - 会话级别： @@ -52,7 +52,7 @@ GUC参数[behavior_compat_options](../../guc-parameters/version-and-platform-com set behavior_compat_options = ''; ``` -- 在驱动为自动提交模式下，用户无需开启此功能，如果开启的话，写命令需要用户显式提交。 +- 在驱动为自动提交模式 (autocommit = on) 下，当驱动版本为JDBC 5.0.0.6/5.0.0.7、Psycopg2 5.0.0.4、ODBC 5.0.0.2时，如果打开此功能，会导致驱动的自动提交模式不生效。后续驱动版本会解决此冲突问题，临时解决方案是在驱动连接字符串里关闭此参数。 ## 各场景下自动提交事务行为 diff --git a/product/zh/docs-mogdb/v5.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/zh/docs-mogdb/v5.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md index 52b903e4afa9e8b0539b8e91a29b15ca0c3d0fc5..f53c9cde793c28b12a199e3f1493ebf24e45b7b3 100644 --- a/product/zh/docs-mogdb/v5.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md +++ b/product/zh/docs-mogdb/v5.1/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md @@ -13,7 +13,7 @@ date: 2021-03-04 数据库支持的索引类型为B-tree索引，例行重建索引可有效的提高查询效率。 -- 如果数据发生大量删除后，索引页面上的索引键将被删除，导致索引页面数量的减少，造成索引膨胀。重建索引可回收浪费的空间。 +- 如果数据发生大量删除后，索引页面上的索引键将被删除，但索引页面并不会直接删除，即索引页面数量并不会减少，因此会造成索引膨胀。重建索引可回收浪费的空间。 - 新建的索引中逻辑结构相邻的页面，通常在物理结构中也是相邻的，所以一个新建的索引比更新了多次的索引访问速度要快。