From d888f75c9338af375fed8c2ea675932115c87c53 Mon Sep 17 00:00:00 2001 From: spaceoddity91719 Date: Tue, 2 Jul 2024 17:55:17 +0800 Subject: [PATCH 1/3] =?UTF-8?q?fix(mogdb):BRIN=E5=92=8CBLOOM=E7=B4=A2?= =?UTF-8?q?=E5=BC=95=E6=B7=BB=E5=8A=A0=E7=BA=A6=E6=9D=9F?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ .../enterprise-level-features/24-brin-index.md | 4 ++++ .../enterprise-level-features/25-bloom-index.md | 4 ++++ 20 files changed, 80 insertions(+) diff --git a/product/en/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/24-brin-index.md b/product/en/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/24-brin-index.md index b17d90ae..f8e91348 100644 --- a/product/en/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/en/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ The way a BRIN index works: The block of a table is divided into some intervals, The BRIN index is suitable for columns where the data is correlated with the physical location. The optimizer uses this value to make a choice between an index scan and a bitmap scan. We can also use it to estimate how well the BRIN index fits. The closer the column position correlation is to 1, the more correlated the column data is and the more suitable for building a BRIN index. Also BRIN indexes are mainly designed for large tables. Compared with indexes like btree, BRIN indexes have less data volume. +## Constrains + +- BRIN indexes are not supported in B-compatible mode databases. + ## Scenarios ### Create a BRIN Index diff --git a/product/en/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/en/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/25-bloom-index.md index 5ad1e2b5..487f44c6 100644 --- a/product/en/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/en/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom indexes are suitable for scenarios where there are many columns in a table Users can query through Bloom index in the applicable scenario of Bloom index, and also reduce the size of index space occupied compared with Btree index. +## Constrains + +- BLOOM indexes are not supported in B-compatible mode databases. + ## Scenarios Blooms indexes are most useful when the table has many attributes and the query may test any combination of them. Traditional btree indexes will be faster than Bloom indexes, but many btree indexes are needed to support all possible queries, while for Bloom only one is needed. diff --git a/product/en/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/24-brin-index.md b/product/en/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/24-brin-index.md index f64e69fb..a504990b 100644 --- a/product/en/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/en/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ The way a BRIN index works: The block of a table is divided into some intervals, The BRIN index is suitable for columns where the data is correlated with the physical location. The optimizer uses this value to make a choice between an index scan and a bitmap scan. We can also use it to estimate how well the BRIN index fits. The closer the column position correlation is to 1, the more correlated the column data is and the more suitable for building a BRIN index. Also BRIN indexes are mainly designed for large tables. Compared with indexes like btree, BRIN indexes have less data volume. +## Constrains + +- BRIN indexes are not supported in B-compatible mode databases. + ## Scenarios ### Create a BRIN Index diff --git a/product/en/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/en/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/25-bloom-index.md index 5e60686b..6c4b8429 100644 --- a/product/en/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/en/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom indexes are suitable for scenarios where there are many columns in a table Users can query through Bloom index in the applicable scenario of Bloom index, and also reduce the size of index space occupied compared with Btree index. +## Constrains + +- BLOOM indexes are not supported in B-compatible mode databases. + ## Scenarios Blooms indexes are most useful when the table has many attributes and the query may test any combination of them. Traditional btree indexes will be faster than Bloom indexes, but many btree indexes are needed to support all possible queries, while for Bloom only one is needed. diff --git a/product/en/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/24-brin-index.md b/product/en/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/24-brin-index.md index f64e69fb..a504990b 100644 --- a/product/en/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/en/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ The way a BRIN index works: The block of a table is divided into some intervals, The BRIN index is suitable for columns where the data is correlated with the physical location. The optimizer uses this value to make a choice between an index scan and a bitmap scan. We can also use it to estimate how well the BRIN index fits. The closer the column position correlation is to 1, the more correlated the column data is and the more suitable for building a BRIN index. Also BRIN indexes are mainly designed for large tables. Compared with indexes like btree, BRIN indexes have less data volume. +## Constrains + +- BRIN indexes are not supported in B-compatible mode databases. + ## Scenarios ### Create a BRIN Index diff --git a/product/en/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/en/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/25-bloom-index.md index 5e60686b..6c4b8429 100644 --- a/product/en/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/en/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom indexes are suitable for scenarios where there are many columns in a table Users can query through Bloom index in the applicable scenario of Bloom index, and also reduce the size of index space occupied compared with Btree index. +## Constrains + +- BLOOM indexes are not supported in B-compatible mode databases. + ## Scenarios Blooms indexes are most useful when the table has many attributes and the query may test any combination of them. Traditional btree indexes will be faster than Bloom indexes, but many btree indexes are needed to support all possible queries, while for Bloom only one is needed. diff --git a/product/en/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/24-brin-index.md b/product/en/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/24-brin-index.md index f64e69fb..a504990b 100644 --- a/product/en/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/en/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ The way a BRIN index works: The block of a table is divided into some intervals, The BRIN index is suitable for columns where the data is correlated with the physical location. The optimizer uses this value to make a choice between an index scan and a bitmap scan. We can also use it to estimate how well the BRIN index fits. The closer the column position correlation is to 1, the more correlated the column data is and the more suitable for building a BRIN index. Also BRIN indexes are mainly designed for large tables. Compared with indexes like btree, BRIN indexes have less data volume. +## Constrains + +- BRIN indexes are not supported in B-compatible mode databases. + ## Scenarios ### Create a BRIN Index diff --git a/product/en/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/en/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/25-bloom-index.md index 5e60686b..6c4b8429 100644 --- a/product/en/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/en/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom indexes are suitable for scenarios where there are many columns in a table Users can query through Bloom index in the applicable scenario of Bloom index, and also reduce the size of index space occupied compared with Btree index. +## Constrains + +- BLOOM indexes are not supported in B-compatible mode databases. + ## Scenarios Blooms indexes are most useful when the table has many attributes and the query may test any combination of them. Traditional btree indexes will be faster than Bloom indexes, but many btree indexes are needed to support all possible queries, while for Bloom only one is needed. diff --git a/product/en/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/24-brin-index.md b/product/en/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/24-brin-index.md index f64e69fb..a504990b 100644 --- a/product/en/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/en/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ The way a BRIN index works: The block of a table is divided into some intervals, The BRIN index is suitable for columns where the data is correlated with the physical location. The optimizer uses this value to make a choice between an index scan and a bitmap scan. We can also use it to estimate how well the BRIN index fits. The closer the column position correlation is to 1, the more correlated the column data is and the more suitable for building a BRIN index. Also BRIN indexes are mainly designed for large tables. Compared with indexes like btree, BRIN indexes have less data volume. +## Constrains + +- BRIN indexes are not supported in B-compatible mode databases. + ## Scenarios ### Create a BRIN Index diff --git a/product/en/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/en/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/25-bloom-index.md index 5e60686b..6c4b8429 100644 --- a/product/en/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/en/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom indexes are suitable for scenarios where there are many columns in a table Users can query through Bloom index in the applicable scenario of Bloom index, and also reduce the size of index space occupied compared with Btree index. +## Constrains + +- BLOOM indexes are not supported in B-compatible mode databases. + ## Scenarios Blooms indexes are most useful when the table has many attributes and the query may test any combination of them. Traditional btree indexes will be faster than Bloom indexes, but many btree indexes are needed to support all possible queries, while for Bloom only one is needed. diff --git a/product/zh/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/24-brin-index.md b/product/zh/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/24-brin-index.md index 3e77dc75..e5a50de5 100644 --- a/product/zh/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/zh/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ BRIN索引的工作方式：表的块被划分成一些区间，索引存储了 BRIN索引适合数据与物理位置有相关性的列。优化器使用这个值来从索引扫描和位图扫描中做选择。我们也可以使用它估计BRIN索引的适合程度。列的位置相关性越接近1，则列数据的相关性越强，越适合建BRIN索引。另外BRIN索引主要是为大表而设计的，相比于btree等索引，BRIN索引的数据量较小。 +## 特性约束 + +- B兼容模式不支持BRIN索引。 + ## 使用场景 ### 创建BRIN索引 diff --git a/product/zh/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/zh/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/25-bloom-index.md index 4ad81f2e..4ffb1d1b 100644 --- a/product/zh/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/zh/docs-mogdb/v3.0/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom索引适用于表中有很多列，并且查询可以使用任意列组合 用户在Bloom索引的适用场景下可以通过Bloom索引进行查询，同时相对于Btree索引还可以减少索引占用空间大小。 +## 特性约束 + +- B兼容模式不支持BLOOM索引。 + ## 使用场景 当表具有很多属性并且查询可能会测试其中任意组合时，Blooms类型的索引最有用，传统的btree索引会比Bloom索引更快，但需要很多btree索引来支持所有可能的查询，而对于Bloom只需要一个即可。 diff --git a/product/zh/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/24-brin-index.md b/product/zh/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/24-brin-index.md index d34be1fa..c42e6019 100644 --- a/product/zh/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/zh/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ BRIN索引的工作方式：表的块被划分成一些区间，索引存储了 BRIN索引适合数据与物理位置有相关性的列。优化器使用这个值来从索引扫描和位图扫描中做选择。我们也可以使用它估计BRIN索引的适合程度。列的位置相关性越接近1，则列数据的相关性越强，越适合建BRIN索引。另外BRIN索引主要是为大表而设计的，相比于btree等索引，BRIN索引的数据量较小。 +## 特性约束 + +- B兼容模式不支持BRIN索引。 + ## 使用场景 ### 创建BRIN索引 diff --git a/product/zh/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/zh/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/25-bloom-index.md index 6c8b1ad1..9dc64c20 100644 --- a/product/zh/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/zh/docs-mogdb/v3.1/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom索引适用于表中有很多列，并且查询可以使用任意列组合 用户在Bloom索引的适用场景下可以通过Bloom索引进行查询，同时相对于Btree索引还可以减少索引占用空间大小。 +## 特性约束 + +- B兼容模式不支持BLOOM索引。 + ## 使用场景 当表具有很多属性并且查询可能会测试其中任意组合时，Blooms类型的索引最有用，传统的btree索引会比Bloom索引更快，但需要很多btree索引来支持所有可能的查询，而对于Bloom只需要一个即可。 diff --git a/product/zh/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/24-brin-index.md b/product/zh/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/24-brin-index.md index d34be1fa..c42e6019 100644 --- a/product/zh/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/zh/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ BRIN索引的工作方式：表的块被划分成一些区间，索引存储了 BRIN索引适合数据与物理位置有相关性的列。优化器使用这个值来从索引扫描和位图扫描中做选择。我们也可以使用它估计BRIN索引的适合程度。列的位置相关性越接近1，则列数据的相关性越强，越适合建BRIN索引。另外BRIN索引主要是为大表而设计的，相比于btree等索引，BRIN索引的数据量较小。 +## 特性约束 + +- B兼容模式不支持BRIN索引。 + ## 使用场景 ### 创建BRIN索引 diff --git a/product/zh/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/zh/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/25-bloom-index.md index 6c8b1ad1..9dc64c20 100644 --- a/product/zh/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/zh/docs-mogdb/v5.0/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom索引适用于表中有很多列，并且查询可以使用任意列组合 用户在Bloom索引的适用场景下可以通过Bloom索引进行查询，同时相对于Btree索引还可以减少索引占用空间大小。 +## 特性约束 + +- B兼容模式不支持BLOOM索引。 + ## 使用场景 当表具有很多属性并且查询可能会测试其中任意组合时，Blooms类型的索引最有用，传统的btree索引会比Bloom索引更快，但需要很多btree索引来支持所有可能的查询，而对于Bloom只需要一个即可。 diff --git a/product/zh/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/24-brin-index.md b/product/zh/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/24-brin-index.md index d34be1fa..c42e6019 100644 --- a/product/zh/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/zh/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ BRIN索引的工作方式：表的块被划分成一些区间，索引存储了 BRIN索引适合数据与物理位置有相关性的列。优化器使用这个值来从索引扫描和位图扫描中做选择。我们也可以使用它估计BRIN索引的适合程度。列的位置相关性越接近1，则列数据的相关性越强，越适合建BRIN索引。另外BRIN索引主要是为大表而设计的，相比于btree等索引，BRIN索引的数据量较小。 +## 特性约束 + +- B兼容模式不支持BRIN索引。 + ## 使用场景 ### 创建BRIN索引 diff --git a/product/zh/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/zh/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/25-bloom-index.md index 6c8b1ad1..9dc64c20 100644 --- a/product/zh/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/zh/docs-mogdb/v5.2/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom索引适用于表中有很多列，并且查询可以使用任意列组合 用户在Bloom索引的适用场景下可以通过Bloom索引进行查询，同时相对于Btree索引还可以减少索引占用空间大小。 +## 特性约束 + +- B兼容模式不支持BLOOM索引。 + ## 使用场景 当表具有很多属性并且查询可能会测试其中任意组合时，Blooms类型的索引最有用，传统的btree索引会比Bloom索引更快，但需要很多btree索引来支持所有可能的查询，而对于Bloom只需要一个即可。 diff --git a/product/zh/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/24-brin-index.md b/product/zh/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/24-brin-index.md index d34be1fa..c42e6019 100644 --- a/product/zh/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/24-brin-index.md +++ b/product/zh/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/24-brin-index.md @@ -31,6 +31,10 @@ BRIN索引的工作方式：表的块被划分成一些区间，索引存储了 BRIN索引适合数据与物理位置有相关性的列。优化器使用这个值来从索引扫描和位图扫描中做选择。我们也可以使用它估计BRIN索引的适合程度。列的位置相关性越接近1，则列数据的相关性越强，越适合建BRIN索引。另外BRIN索引主要是为大表而设计的，相比于btree等索引，BRIN索引的数据量较小。 +## 特性约束 + +- B兼容模式不支持BRIN索引。 + ## 使用场景 ### 创建BRIN索引 diff --git a/product/zh/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/25-bloom-index.md b/product/zh/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/25-bloom-index.md index 6c8b1ad1..9dc64c20 100644 --- a/product/zh/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/25-bloom-index.md +++ b/product/zh/docs-mogdb/v6.0/characteristic-description/enterprise-level-features/25-bloom-index.md @@ -23,6 +23,10 @@ Bloom索引适用于表中有很多列，并且查询可以使用任意列组合 用户在Bloom索引的适用场景下可以通过Bloom索引进行查询，同时相对于Btree索引还可以减少索引占用空间大小。 +## 特性约束 + +- B兼容模式不支持BLOOM索引。 + ## 使用场景 当表具有很多属性并且查询可能会测试其中任意组合时，Blooms类型的索引最有用，传统的btree索引会比Bloom索引更快，但需要很多btree索引来支持所有可能的查询，而对于Bloom只需要一个即可。 -- Gitee From a7b9d1c304b6bab4f2cb90ced57970a4533ea846 Mon Sep 17 00:00:00 2001 From: spaceoddity91719 Date: Tue, 2 Jul 2024 18:03:19 +0800 Subject: [PATCH 2/3] fix(mogdb):issue IA9OAL --- .../en/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md | 4 ++-- .../en/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md | 4 ++-- .../en/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md | 4 ++-- .../zh/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md | 4 ++-- .../zh/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md | 4 ++-- .../zh/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md | 4 ++-- 6 files changed, 12 insertions(+), 12 deletions(-) diff --git a/product/en/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md b/product/en/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md index d14082fb..cbbe75de 100644 --- a/product/en/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md +++ b/product/en/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md @@ -12,7 +12,7 @@ date: 2024-05-17 The upgrade includes the following impacts and constraints, before upgrading, you should do a good job of fully checking and understanding, to ensure that the conditions can be met before upgrading, if you have any questions, please contact our engineers. - Do not perform the upgrade, scale-out, and scale-in at the same time. -- Virtual IP addresses are not supported. +- In-place upgrades do not involve Virtual IP, and CM automatically drift Virtual IP during rolling upgrades. - During the upgrade, do not change the values of **wal_level**, **max_connections**, **max_prepared_transactions**, and **max_locks_per_transaction**. If the value is changed, the instance fails to be started after the rollback. - You are advised to perform upgrade when the database system is idle. You can determine the time (for example, holidays) based on experience. - Before the upgrade, ensure that the database is normal. If your database was installed via PTK, you can run the `ptk cluster -n status` command to query the cluster status, Normal means that all instances of the cluster are available. If your database was installed via gs_om, you can run the `gs_om -t status` command to query the database status. If the value of cluster_state in the query result is Normal, the database is normal. @@ -20,7 +20,7 @@ The upgrade includes the following impacts and constraints, before upgrading, yo - The database deployment mode (configuration files) cannot be changed before and after the upgrade. Before the upgrade, the deployment mode is verified. If the deployment mode is changed, an error is reported. - The database is running properly and data on the primary node has been fully synchronized to standby nodes. - Do not enable Kerberos during the upgrade. -- A cluster that has CM enabled cannot be upgraded, but you can uninstall CM via PTK version 1.4.0 or above, and then upgrade the cluster. +- PTK has supported upgrades of database clusters with CM deployed since version 1.5. - The cluster stream replication parameter `enable_stream_replication` needs to be set to `on`.
diff --git a/product/en/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md b/product/en/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md index d14082fb..cbbe75de 100644 --- a/product/en/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md +++ b/product/en/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md @@ -12,7 +12,7 @@ date: 2024-05-17 The upgrade includes the following impacts and constraints, before upgrading, you should do a good job of fully checking and understanding, to ensure that the conditions can be met before upgrading, if you have any questions, please contact our engineers. - Do not perform the upgrade, scale-out, and scale-in at the same time. -- Virtual IP addresses are not supported. +- In-place upgrades do not involve Virtual IP, and CM automatically drift Virtual IP during rolling upgrades. - During the upgrade, do not change the values of **wal_level**, **max_connections**, **max_prepared_transactions**, and **max_locks_per_transaction**. If the value is changed, the instance fails to be started after the rollback. - You are advised to perform upgrade when the database system is idle. You can determine the time (for example, holidays) based on experience. - Before the upgrade, ensure that the database is normal. If your database was installed via PTK, you can run the `ptk cluster -n status` command to query the cluster status, Normal means that all instances of the cluster are available. If your database was installed via gs_om, you can run the `gs_om -t status` command to query the database status. If the value of cluster_state in the query result is Normal, the database is normal. @@ -20,7 +20,7 @@ The upgrade includes the following impacts and constraints, before upgrading, yo - The database deployment mode (configuration files) cannot be changed before and after the upgrade. Before the upgrade, the deployment mode is verified. If the deployment mode is changed, an error is reported. - The database is running properly and data on the primary node has been fully synchronized to standby nodes. - Do not enable Kerberos during the upgrade. -- A cluster that has CM enabled cannot be upgraded, but you can uninstall CM via PTK version 1.4.0 or above, and then upgrade the cluster. +- PTK has supported upgrades of database clusters with CM deployed since version 1.5. - The cluster stream replication parameter `enable_stream_replication` needs to be set to `on`.
diff --git a/product/en/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md b/product/en/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md index c88cc616..51f86831 100644 --- a/product/en/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md +++ b/product/en/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md @@ -12,7 +12,7 @@ date: 2024-05-17 The upgrade includes the following impacts and constraints, before upgrading, you should do a good job of fully checking and understanding, to ensure that the conditions can be met before upgrading, if you have any questions, please contact our engineers. - Do not perform the upgrade, scale-out, and scale-in at the same time. -- Virtual IP addresses are not supported. +- In-place upgrades do not involve Virtual IP, and CM automatically drift Virtual IP during rolling upgrades. - During the upgrade, do not change the values of **wal_level**, **max_connections**, **max_prepared_transactions**, and **max_locks_per_transaction**. If the value is changed, the instance fails to be started after the rollback. - You are advised to perform upgrade when the database system is idle. You can determine the time (for example, holidays) based on experience. - Before the upgrade, ensure that the database is normal. If your database was installed via PTK, you can run the `ptk cluster -n status` command to query the cluster status, Normal means that all instances of the cluster are available. If your database was installed via gs_om, you can run the `gs_om -t status` command to query the database status. If the value of cluster_state in the query result is Normal, the database is normal. @@ -20,7 +20,7 @@ The upgrade includes the following impacts and constraints, before upgrading, yo - The database deployment mode (configuration files) cannot be changed before and after the upgrade. Before the upgrade, the deployment mode is verified. If the deployment mode is changed, an error is reported. - The database is running properly and data on the primary node has been fully synchronized to standby nodes. - Do not enable Kerberos during the upgrade. -- A cluster that has CM enabled cannot be upgraded, but you can uninstall CM via PTK version 1.4.0 or above, and then upgrade the cluster. +- PTK has supported upgrades of database clusters with CM deployed since version 1.5. - The cluster stream replication parameter `enable_stream_replication` needs to be set to `on`.
diff --git a/product/zh/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md b/product/zh/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md index d2165140..76be9501 100644 --- a/product/zh/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md +++ b/product/zh/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md @@ -12,7 +12,7 @@ date: 2024-05-17 升级包含以下影响和约束，在升级前应该做好充分检查和了解，确保条件都能满足的情况下再进行升级，如果有任何疑问需联系原厂工程师。 - 升级操作不能和扩容、缩容同时执行。 -- 不支持虚拟IP。 +- 就地升级不涉及VIP，滚动升级期间CM会自动漂移VIP。 - 升级过程中，不允许对wal_level，max_connections，max_prepared_transactions，max_locks_per_transaction这四个GUC参数的值进行修改。如果修改，会导致回滚后实例启动异常。 - 建议在数据库系统空闲情况下进行升级，尽量避开业务繁忙的时间段（可按照经验判断，如节假日等）。 - 升级前尽可能保证数据库状态正常。通过PTK安装的版本可通过`ptk cluster -n status`命令查看集群状态，Normal代表集群所有实例正常可用。通过OM安装的版本可以通过`gs_om -t status`查询，查询结果的cluster_state为Normal代表数据库正常可用。 @@ -20,7 +20,7 @@ date: 2024-05-17 - 升级前后，数据库的部署方式（配置文件）不能发生变化。升级前PTK会对部署方式进行校验，如果改变会报错。 - 数据库运行正常且主DN的数据完全同步到备DN。 - 升级过程中不允许打开kerberos开关。 -- 暂不支持部署了CM的集群升级，可通过PTK 1.4.0以上的版本卸载CM后升级。 +- PTK自1.5版本开始支持部署了CM的数据库集群的升级。 - 集群流复制参数需开启（enable_stream_replication）。
diff --git a/product/zh/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md b/product/zh/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md index d2165140..76be9501 100644 --- a/product/zh/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md +++ b/product/zh/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md @@ -12,7 +12,7 @@ date: 2024-05-17 升级包含以下影响和约束，在升级前应该做好充分检查和了解，确保条件都能满足的情况下再进行升级，如果有任何疑问需联系原厂工程师。 - 升级操作不能和扩容、缩容同时执行。 -- 不支持虚拟IP。 +- 就地升级不涉及VIP，滚动升级期间CM会自动漂移VIP。 - 升级过程中，不允许对wal_level，max_connections，max_prepared_transactions，max_locks_per_transaction这四个GUC参数的值进行修改。如果修改，会导致回滚后实例启动异常。 - 建议在数据库系统空闲情况下进行升级，尽量避开业务繁忙的时间段（可按照经验判断，如节假日等）。 - 升级前尽可能保证数据库状态正常。通过PTK安装的版本可通过`ptk cluster -n status`命令查看集群状态，Normal代表集群所有实例正常可用。通过OM安装的版本可以通过`gs_om -t status`查询，查询结果的cluster_state为Normal代表数据库正常可用。 @@ -20,7 +20,7 @@ date: 2024-05-17 - 升级前后，数据库的部署方式（配置文件）不能发生变化。升级前PTK会对部署方式进行校验，如果改变会报错。 - 数据库运行正常且主DN的数据完全同步到备DN。 - 升级过程中不允许打开kerberos开关。 -- 暂不支持部署了CM的集群升级，可通过PTK 1.4.0以上的版本卸载CM后升级。 +- PTK自1.5版本开始支持部署了CM的数据库集群的升级。 - 集群流复制参数需开启（enable_stream_replication）。
diff --git a/product/zh/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md b/product/zh/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md index 125462bc..c00718b6 100644 --- a/product/zh/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md +++ b/product/zh/docs-mogdb/v6.0/upgrade-guide/2-read-before-upgrade.md @@ -12,7 +12,7 @@ date: 2024-05-17 升级包含以下影响和约束，在升级前应该做好充分检查和了解，确保条件都能满足的情况下再进行升级，如果有任何疑问需联系原厂工程师。 - 升级操作不能和扩容、缩容同时执行。 -- 不支持虚拟IP。 +- 就地升级不涉及VIP，滚动升级期间CM会自动漂移VIP。 - 升级过程中，不允许对wal_level，max_connections，max_prepared_transactions，max_locks_per_transaction这四个GUC参数的值进行修改。如果修改，会导致回滚后实例启动异常。 - 建议在数据库系统空闲情况下进行升级，尽量避开业务繁忙的时间段（可按照经验判断，如节假日等）。 - 升级前尽可能保证数据库状态正常。通过PTK安装的版本可通过`ptk cluster -n status`命令查看集群状态，Normal代表集群所有实例正常可用。通过OM安装的版本可以通过`gs_om -t status`查询，查询结果的cluster_state为Normal代表数据库正常可用。 @@ -20,7 +20,7 @@ date: 2024-05-17 - 升级前后，数据库的部署方式（配置文件）不能发生变化。升级前PTK会对部署方式进行校验，如果改变会报错。 - 数据库运行正常且主DN的数据完全同步到备DN。 - 升级过程中不允许打开kerberos开关。 -- 暂不支持部署了CM的集群升级，可通过PTK 1.4.0以上的版本卸载CM后升级。 +- PTK自1.5版本开始支持部署了CM的数据库集群的升级。 - 集群流复制参数需开启（enable_stream_replication）。
-- Gitee From 5c28745d2ea2271626df382fdd9429a5381b81a8 Mon Sep 17 00:00:00 2001 From: spaceoddity91719 Date: Tue, 2 Jul 2024 18:13:27 +0800 Subject: [PATCH 3/3] fix(mogdb):issues IA9WYS --- .../functions-and-operators/23-system-information-functions.md | 2 -- .../functions-and-operators/23-system-information-functions.md | 2 -- .../functions-and-operators/23-system-information-functions.md | 2 -- .../functions-and-operators/23-system-information-functions.md | 2 -- .../system-catalog-information-functions.md | 2 -- .../system-catalog-information-functions.md | 2 -- .../system-catalog-information-functions.md | 2 -- .../system-catalog-information-functions.md | 2 -- .../functions-and-operators/23-system-information-functions.md | 2 -- .../functions-and-operators/23-system-information-functions.md | 2 -- .../functions-and-operators/23-system-information-functions.md | 2 -- .../functions-and-operators/23-system-information-functions.md | 2 -- .../system-catalog-information-functions.md | 2 -- .../system-catalog-information-functions.md | 2 -- .../system-catalog-information-functions.md | 2 -- .../system-catalog-information-functions.md | 2 -- 16 files changed, 32 deletions(-) diff --git a/product/en/docs-mogdb/v1.1/reference-guide/functions-and-operators/23-system-information-functions.md b/product/en/docs-mogdb/v1.1/reference-guide/functions-and-operators/23-system-information-functions.md index 4074cd9c..7d4fea74 100644 --- a/product/en/docs-mogdb/v1.1/reference-guide/functions-and-operators/23-system-information-functions.md +++ b/product/en/docs-mogdb/v1.1/reference-guide/functions-and-operators/23-system-information-functions.md @@ -1126,8 +1126,6 @@ mogdb=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid); Return type: text - Note:**pg_get_functiondef** returns a complete **CREATE OR REPLACE FUNCTION** statement for a function. - - pg_get_keywords() Description: Gets list of SQL keywords and their categories. diff --git a/product/en/docs-mogdb/v2.0/reference-guide/functions-and-operators/23-system-information-functions.md b/product/en/docs-mogdb/v2.0/reference-guide/functions-and-operators/23-system-information-functions.md index 95ebca39..ac25a34a 100644 --- a/product/en/docs-mogdb/v2.0/reference-guide/functions-and-operators/23-system-information-functions.md +++ b/product/en/docs-mogdb/v2.0/reference-guide/functions-and-operators/23-system-information-functions.md @@ -1126,8 +1126,6 @@ mogdb=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid); Return type: text - Note:**pg_get_functiondef** returns a complete **CREATE OR REPLACE FUNCTION** statement for a function. - - pg_get_keywords() Description: Gets list of SQL keywords and their categories. diff --git a/product/en/docs-mogdb/v2.1/reference-guide/functions-and-operators/23-system-information-functions.md b/product/en/docs-mogdb/v2.1/reference-guide/functions-and-operators/23-system-information-functions.md index 6ea3bbbc..d595ea80 100644 --- a/product/en/docs-mogdb/v2.1/reference-guide/functions-and-operators/23-system-information-functions.md +++ b/product/en/docs-mogdb/v2.1/reference-guide/functions-and-operators/23-system-information-functions.md @@ -1169,8 +1169,6 @@ mogdb=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid); Return type: text - Note: **pg_get_functiondef** returns a complete **CREATE OR REPLACE FUNCTION** statement for a function. - - pg_get_keywords() Description: Obtains the list of SQL keywords and their categories. diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md index f441ae10..a3ec7999 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md @@ -1189,8 +1189,6 @@ MogDB=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid); Return type: text - Note: **pg_get_functiondef** returns a complete **CREATE OR REPLACE FUNCTION** statement for a function. - - pg_get_keywords() Description: Obtains the list of SQL keywords and their categories. diff --git a/product/en/docs-mogdb/v3.1/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md b/product/en/docs-mogdb/v3.1/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md index ab1bc668..69e584db 100644 --- a/product/en/docs-mogdb/v3.1/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md +++ b/product/en/docs-mogdb/v3.1/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md @@ -210,8 +210,6 @@ date: 2021-04-20 Return type: text - Note: **pg_get_functiondef** returns a complete **CREATE OR REPLACE FUNCTION** statement for a function. - - pg_get_keywords() Description: Obtains the list of SQL keywords and their categories. diff --git a/product/en/docs-mogdb/v5.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md b/product/en/docs-mogdb/v5.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md index ec9f1547..74244fc8 100644 --- a/product/en/docs-mogdb/v5.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md +++ b/product/en/docs-mogdb/v5.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md @@ -210,8 +210,6 @@ date: 2021-04-20 Return type: text - Note: **pg_get_functiondef** returns a complete **CREATE OR REPLACE FUNCTION** statement for a function. - - pg_get_keywords() Description: Obtains the list of SQL keywords and their categories. diff --git a/product/en/docs-mogdb/v5.2/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md b/product/en/docs-mogdb/v5.2/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md index ec9f1547..74244fc8 100644 --- a/product/en/docs-mogdb/v5.2/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md +++ b/product/en/docs-mogdb/v5.2/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md @@ -210,8 +210,6 @@ date: 2021-04-20 Return type: text - Note: **pg_get_functiondef** returns a complete **CREATE OR REPLACE FUNCTION** statement for a function. - - pg_get_keywords() Description: Obtains the list of SQL keywords and their categories. diff --git a/product/en/docs-mogdb/v6.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md b/product/en/docs-mogdb/v6.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md index ec9f1547..74244fc8 100644 --- a/product/en/docs-mogdb/v6.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md +++ b/product/en/docs-mogdb/v6.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md @@ -210,8 +210,6 @@ date: 2021-04-20 Return type: text - Note: **pg_get_functiondef** returns a complete **CREATE OR REPLACE FUNCTION** statement for a function. - - pg_get_keywords() Description: Obtains the list of SQL keywords and their categories. diff --git a/product/zh/docs-mogdb/v1.1/reference-guide/functions-and-operators/23-system-information-functions.md b/product/zh/docs-mogdb/v1.1/reference-guide/functions-and-operators/23-system-information-functions.md index 4d211e5a..7a2d8e63 100644 --- a/product/zh/docs-mogdb/v1.1/reference-guide/functions-and-operators/23-system-information-functions.md +++ b/product/zh/docs-mogdb/v1.1/reference-guide/functions-and-operators/23-system-information-functions.md @@ -1112,8 +1112,6 @@ mogdb=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid); 返回类型: text - 备注: pg_get_functiondef为函数返回一个完整的CREATE OR REPLACE FUNCTION语句。 - - pg_get_keywords() 描述: 获取SQL关键字和类别列表 diff --git a/product/zh/docs-mogdb/v2.0/reference-guide/functions-and-operators/23-system-information-functions.md b/product/zh/docs-mogdb/v2.0/reference-guide/functions-and-operators/23-system-information-functions.md index 3f637a63..5c5565c5 100644 --- a/product/zh/docs-mogdb/v2.0/reference-guide/functions-and-operators/23-system-information-functions.md +++ b/product/zh/docs-mogdb/v2.0/reference-guide/functions-and-operators/23-system-information-functions.md @@ -1112,8 +1112,6 @@ mogdb=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid); 返回类型: text - 备注: pg_get_functiondef为函数返回一个完整的CREATE OR REPLACE FUNCTION语句。 - - pg_get_keywords() 描述: 获取SQL关键字和类别列表 diff --git a/product/zh/docs-mogdb/v2.1/reference-guide/functions-and-operators/23-system-information-functions.md b/product/zh/docs-mogdb/v2.1/reference-guide/functions-and-operators/23-system-information-functions.md index 1ed73bd5..d8a08325 100644 --- a/product/zh/docs-mogdb/v2.1/reference-guide/functions-and-operators/23-system-information-functions.md +++ b/product/zh/docs-mogdb/v2.1/reference-guide/functions-and-operators/23-system-information-functions.md @@ -1168,8 +1168,6 @@ mogdb=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid); 返回类型：text - 备注：pg_get_functiondef为函数返回一个完整的CREATE OR REPLACE FUNCTION语句。 - - pg_get_keywords() 描述：获取SQL关键字和类别列表。 diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md index 05c5eac9..3b0a8739 100644 --- a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md +++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md @@ -1187,8 +1187,6 @@ MogDB=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid); 返回类型：text - 备注：pg_get_functiondef为函数返回一个完整的CREATE OR REPLACE FUNCTION语句。 - - pg_get_keywords() 描述：获取SQL关键字和类别列表。 diff --git a/product/zh/docs-mogdb/v3.1/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md b/product/zh/docs-mogdb/v3.1/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md index aeeba095..be41aeb8 100644 --- a/product/zh/docs-mogdb/v3.1/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md +++ b/product/zh/docs-mogdb/v3.1/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md @@ -210,8 +210,6 @@ date: 2021-04-20 返回类型：text - 备注：pg_get_functiondef为函数返回一个完整的CREATE OR REPLACE FUNCTION语句。 - - pg_get_keywords() 描述：获取SQL关键字和类别列表。 diff --git a/product/zh/docs-mogdb/v5.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md b/product/zh/docs-mogdb/v5.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md index c014e72e..d2682099 100644 --- a/product/zh/docs-mogdb/v5.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md +++ b/product/zh/docs-mogdb/v5.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md @@ -210,8 +210,6 @@ date: 2021-04-20 返回类型：text - 备注：pg_get_functiondef为函数返回一个完整的CREATE OR REPLACE FUNCTION语句。 - - pg_get_keywords() 描述：获取SQL关键字和类别列表。 diff --git a/product/zh/docs-mogdb/v5.2/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md b/product/zh/docs-mogdb/v5.2/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md index c014e72e..d2682099 100644 --- a/product/zh/docs-mogdb/v5.2/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md +++ b/product/zh/docs-mogdb/v5.2/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md @@ -210,8 +210,6 @@ date: 2021-04-20 返回类型：text - 备注：pg_get_functiondef为函数返回一个完整的CREATE OR REPLACE FUNCTION语句。 - - pg_get_keywords() 描述：获取SQL关键字和类别列表。 diff --git a/product/zh/docs-mogdb/v6.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md b/product/zh/docs-mogdb/v6.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md index c014e72e..d2682099 100644 --- a/product/zh/docs-mogdb/v6.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md +++ b/product/zh/docs-mogdb/v6.0/reference-guide/functions-and-operators/system-information-functions/system-catalog-information-functions.md @@ -210,8 +210,6 @@ date: 2021-04-20 返回类型：text - 备注：pg_get_functiondef为函数返回一个完整的CREATE OR REPLACE FUNCTION语句。 - - pg_get_keywords() 描述：获取SQL关键字和类别列表。 -- Gitee