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 4074cd9c16c5a4da9c0c336e4756cc3a92e6ba62..7d4fea740738e71feda6b26e56ef6c718e744e76 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 95ebca3902ff8243bdc46dbb232f2cd76d9c6203..ac25a34ac3b9d076eda711e0ea61f00a5a3ad156 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 6ea3bbbc76b3f25e7c68146046f877183598b68f..d595ea80cfb3569dfc8148db19ddf4b3016c6fd3 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/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 b17d90ae410511cc05136a13f0963aba28d787bb..f8e91348a38e8a9322f6b6e3435edfb364ec29c3 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 5ad1e2b5dfa29d75a0b8aed247ad69f51563a649..487f44c6c32a664d0de483bcdd7e528fe7ab6d96 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.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 f441ae107a075a4ddd981881366e7d6a091fb932..a3ec7999d74a9edbb1b3e95309fd7ebe6462a5d9 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/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 f64e69fbc89b2d7f0a3076884f4a9a58cf15a3fe..a504990b72f9e47b9e29c99571ff28b744497a29 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 5e60686b1b77549f6fd0abdd33be7404bfe4bc91..6c4b8429bfb7c8f7910fa4723885a4c963994cd2 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/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 ab1bc668393c09ac2fb7a2f6328169ac57678011..69e584dbf90c5d46b05fd6325b6c097bc3976310 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/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 f64e69fbc89b2d7f0a3076884f4a9a58cf15a3fe..a504990b72f9e47b9e29c99571ff28b744497a29 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 5e60686b1b77549f6fd0abdd33be7404bfe4bc91..6c4b8429bfb7c8f7910fa4723885a4c963994cd2 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.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 ec9f1547d9da83818a4af405c4a2373596ed3b4b..74244fc833c4feec8f1a3c5c105fb0ce58985895 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.0/upgrade-guide/2-read-before-upgrade.md b/product/en/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md index d14082fbca0847bd36d07dbcd66cf54273c626fc..cbbe75de7b0ced8be63630843ead8969fc89b789 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/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 f64e69fbc89b2d7f0a3076884f4a9a58cf15a3fe..a504990b72f9e47b9e29c99571ff28b744497a29 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 5e60686b1b77549f6fd0abdd33be7404bfe4bc91..6c4b8429bfb7c8f7910fa4723885a4c963994cd2 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/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 ec9f1547d9da83818a4af405c4a2373596ed3b4b..74244fc833c4feec8f1a3c5c105fb0ce58985895 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/v5.2/upgrade-guide/2-read-before-upgrade.md b/product/en/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md index d14082fbca0847bd36d07dbcd66cf54273c626fc..cbbe75de7b0ced8be63630843ead8969fc89b789 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/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 f64e69fbc89b2d7f0a3076884f4a9a58cf15a3fe..a504990b72f9e47b9e29c99571ff28b744497a29 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 5e60686b1b77549f6fd0abdd33be7404bfe4bc91..6c4b8429bfb7c8f7910fa4723885a4c963994cd2 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/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 ec9f1547d9da83818a4af405c4a2373596ed3b4b..74244fc833c4feec8f1a3c5c105fb0ce58985895 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/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 c88cc61690a07d6f0a726e3bf71c27e0573fc569..51f86831ac74bf175406c95dc1fdf747f518a6f2 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/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 4d211e5ad6b7e0c04a32c84d7a30f942c194bdf2..7a2d8e637bfb566b189f9caf9415bdc206cbbb73 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 3f637a637d87a32e489c27b4ba84e1c53748c154..5c5565c5fef118c114a76d316b82f75679ab3417 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 1ed73bd560b4358df15c0db94c3969548030de4a..d8a08325d1ceeb97ed03229da42c20da16539b9c 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/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 3e77dc75b776e01f2128236bf127d08c57af2e3b..e5a50de53537206ec9d01f3e695c86f5f882907a 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 4ad81f2e50e787f6cd59ab1af0a229a34dd28889..4ffb1d1b6e997e7913c1db58d3daec970b5ac22d 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.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 05c5eac94baa2f5ee655494221c0277e772e1230..3b0a87394b09dd9c36c689f6e119dc27dca95fac 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/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 d34be1fa0e03d800020d4a2acf237d072be4587a..c42e60191e11433894433bc299bacb2b3ec353d6 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 6c8b1ad19107d0024485e30b633af06f17cc5153..9dc64c20e4109eff3866b1501f6dc29eec772260 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/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 aeeba095f7c30b831132f17020885a4752247fa3..be41aeb8ee8fdbe1df012b6b56a24149b95fca08 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/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 d34be1fa0e03d800020d4a2acf237d072be4587a..c42e60191e11433894433bc299bacb2b3ec353d6 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 6c8b1ad19107d0024485e30b633af06f17cc5153..9dc64c20e4109eff3866b1501f6dc29eec772260 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.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 c014e72e469a5c2484a8da85aff3517f3f8563d8..d268209908438e6987fbf869f3c28e7d737759b5 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.0/upgrade-guide/2-read-before-upgrade.md b/product/zh/docs-mogdb/v5.0/upgrade-guide/2-read-before-upgrade.md index d21651400a51596ea636512a1947d906e3f5a4fc..76be950136ebba6ff813d0530a984e45a383d34b 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/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 d34be1fa0e03d800020d4a2acf237d072be4587a..c42e60191e11433894433bc299bacb2b3ec353d6 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 6c8b1ad19107d0024485e30b633af06f17cc5153..9dc64c20e4109eff3866b1501f6dc29eec772260 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/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 c014e72e469a5c2484a8da85aff3517f3f8563d8..d268209908438e6987fbf869f3c28e7d737759b5 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/v5.2/upgrade-guide/2-read-before-upgrade.md b/product/zh/docs-mogdb/v5.2/upgrade-guide/2-read-before-upgrade.md index d21651400a51596ea636512a1947d906e3f5a4fc..76be950136ebba6ff813d0530a984e45a383d34b 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/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 d34be1fa0e03d800020d4a2acf237d072be4587a..c42e60191e11433894433bc299bacb2b3ec353d6 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 6c8b1ad19107d0024485e30b633af06f17cc5153..9dc64c20e4109eff3866b1501f6dc29eec772260 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只需要一个即可。 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 c014e72e469a5c2484a8da85aff3517f3f8563d8..d268209908438e6987fbf869f3c28e7d737759b5 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关键字和类别列表。 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 125462bc264029913a5bced61ef4baeb9afe8f5e..c00718b61d3e3040b22adf6ca0cbe697c2e3d72d 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）。