From e27c456aef85f21c0d2e721a64e9a2385ebef514 Mon Sep 17 00:00:00 2001 From: spaceoddity91719 Date: Thu, 9 May 2024 14:41:37 +0800 Subject: [PATCH 1/3] =?UTF-8?q?fix(mogdb):select=E4=BA=8B=E5=8A=A1?= =?UTF-8?q?=E8=87=AA=E5=8A=A8=E6=8F=90=E4=BA=A4=E6=96=87=E6=A1=A3=E4=BF=AE?= =?UTF-8?q?=E6=AD=A3?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../sql-reference/transaction/transaction-auto-commit.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 c36467b7..8550b071 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时，如果打开此功能，会导致驱动的自动提交模式不生效。后续驱动版本会解决此冲突问题，临时解决方案是在驱动连接字符串里关闭此参数。 ## 各场景下自动提交事务行为 -- Gitee From d6a909e3679d97445db301a66cfbbf0ca56e58af Mon Sep 17 00:00:00 2001 From: spaceoddity91719 Date: Thu, 9 May 2024 14:49:19 +0800 Subject: [PATCH 2/3] fix(mogdb):fix issue #I8OE2O --- .../docs-mogdb/v1.1/administrator-guide/routine-maintenance.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- .../routine-maintenance/9-routinely-recreating-an-index.md | 2 +- 15 files changed, 15 insertions(+), 15 deletions(-) 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 6b7119a0..1f4c866a 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 cfa38546..0ed746aa 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 cfa38546..0ed746aa 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 cfa38546..0ed746aa 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 0a8c2b31..c5692578 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.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 ac7b37b2..6bfacf4c 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/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 8547ce89..5ddb4d73 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.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 8547ce89..5ddb4d73 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/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 ed733d75..b6da94ab 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 ed733d75..b6da94ab 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 2d8941ed..e8d70ad5 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 42e0e626..d1bc7d58 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.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 52b903e4..f53c9cde 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/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 52b903e4..f53c9cde 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.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 52b903e4..f53c9cde 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索引，例行重建索引可有效的提高查询效率。 -- 如果数据发生大量删除后，索引页面上的索引键将被删除，导致索引页面数量的减少，造成索引膨胀。重建索引可回收浪费的空间。 +- 如果数据发生大量删除后，索引页面上的索引键将被删除，但索引页面并不会直接删除，即索引页面数量并不会减少，因此会造成索引膨胀。重建索引可回收浪费的空间。 - 新建的索引中逻辑结构相邻的页面，通常在物理结构中也是相邻的，所以一个新建的索引比更新了多次的索引访问速度要快。
-- Gitee From 75cd34b40f4f8c215d969f17b217950348d17a7e Mon Sep 17 00:00:00 2001 From: spaceoddity91719 Date: Thu, 9 May 2024 16:48:15 +0800 Subject: [PATCH 3/3] =?UTF-8?q?fix(mogdb):=E5=88=A0=E9=99=A4rocky=20linux?= =?UTF-8?q?=207?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../installation-preparation/environment-requirement.md | 1 - .../installation-preparation/environment-requirement.md | 1 - .../v3.1/quick-start/installation-on-a-single-node.md | 3 +-- .../installation-preparation/environment-requirement.md | 1 - .../installation-preparation/environment-requirement.md | 1 - .../installation-preparation/environment-requirement.md | 1 - .../installation-preparation/environment-requirement.md | 1 - .../v3.1/quick-start/installation-on-a-single-node.md | 3 +-- .../installation-preparation/environment-requirement.md | 1 - 9 files changed, 2 insertions(+), 11 deletions(-) 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 88c2a351..345fa284 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/installation-guide/installation-preparation/environment-requirement.md b/product/en/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md index dece2883..41b026b0 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 2e0be8fd..d13628ea 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/installation-guide/installation-preparation/environment-requirement.md b/product/en/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md index 88c2a351..345fa284 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/installation-guide/installation-preparation/environment-requirement.md b/product/en/docs-mogdb/v5.1/installation-guide/installation-preparation/environment-requirement.md index 88c2a351..345fa284 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/v3.0/installation-guide/installation-preparation/environment-requirement.md b/product/zh/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md index dccddc4e..ade13267 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/installation-guide/installation-preparation/environment-requirement.md b/product/zh/docs-mogdb/v3.1/installation-guide/installation-preparation/environment-requirement.md index 2cc61317..150c997d 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 d6e69362..b6d04df4 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/installation-guide/installation-preparation/environment-requirement.md b/product/zh/docs-mogdb/v5.0/installation-guide/installation-preparation/environment-requirement.md index 8843d729..7068490b 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) | √ | √ | -- Gitee