diff --git a/product/en/docs-mogdb/v1.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/en/docs-mogdb/v1.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 9fbe0358a7d1014e0e056247f870bfc0a219ea27..9c6208074ab3d891a13c7547b472a90ad0b0488a 100644 --- a/product/en/docs-mogdb/v1.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/en/docs-mogdb/v1.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -35,8 +35,6 @@ To measure the run time cost of each node in the execution plan, the current exe Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. -The **EXPLAIN PERFORMANCE** lightweight execution is consistent with **EXPLAIN PERFORMANCE** but greatly reduces the time spent on performance analysis. - ## Description As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail. diff --git a/product/en/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-GROUP.md b/product/en/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-GROUP.md index 897ae2444a98d3cca48a8deeb07facd394ef1525..0b944494a22abc0881561494413c72b0564a60b7 100644 --- a/product/en/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/en/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-GROUP.md @@ -44,7 +44,7 @@ The syntax of the **option** clause is as follows: | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-ROLE.md b/product/en/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-ROLE.md index 7a3d31067c4eb489441cf57db9802a33e6233326..8c1425e33daacee10787a09be5c527f72e9d198f 100644 --- a/product/en/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/en/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-ROLE.md @@ -50,7 +50,7 @@ The syntax of role information configuration clause **option** is as follows: | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v2.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/en/docs-mogdb/v2.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index 8197ee24cc3f44922b4912a678736ed94e77dcb6..31051fe33c6a08de20b768514b6334ec79066bf1 100644 --- a/product/en/docs-mogdb/v2.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/en/docs-mogdb/v2.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -13,7 +13,7 @@ The ODBC driver (psqlodbcw.so) provided by MogDB can be used after it has been c 1. Obtain the source code package of unixODBC. Try the following link: - + [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) After the download, validate the integrity based on the integrity validation algorithm provided by the community. diff --git a/product/en/docs-mogdb/v2.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/en/docs-mogdb/v2.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 9fbe0358a7d1014e0e056247f870bfc0a219ea27..9c6208074ab3d891a13c7547b472a90ad0b0488a 100644 --- a/product/en/docs-mogdb/v2.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/en/docs-mogdb/v2.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -35,8 +35,6 @@ To measure the run time cost of each node in the execution plan, the current exe Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. -The **EXPLAIN PERFORMANCE** lightweight execution is consistent with **EXPLAIN PERFORMANCE** but greatly reduces the time spent on performance analysis. - ## Description As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail. diff --git a/product/en/docs-mogdb/v2.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb.md b/product/en/docs-mogdb/v2.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb.md index 40bf463bbec55c39a1c0823526682879a788bcbb..3c6df6eb0f6d76c8e77698172cf5e4c4e427bd9c 100644 --- a/product/en/docs-mogdb/v2.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb.md +++ b/product/en/docs-mogdb/v2.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb.md @@ -66,7 +66,7 @@ Java 1.8.0_181 or later > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **Note:** > -> * Please refer to [https://www.java.com/en/download/help/path.html](https://www.java.com/en/download/help/path.html) to set the Java Home path. +> * Please refer to [java.com](https://www.java.com/en/download/help/path.html) to set the Java Home path. > * To ensure the optimal experience, the recommended minimum screen resolution is 1080 x 768. Below this resolution, the interface will be abnormal.
diff --git a/product/en/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-GROUP.md b/product/en/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-GROUP.md index 42da346c39a05056006150924ced6785e4e02331..aa3a4414c162e2080ba676c72e1992346ff1e88e 100644 --- a/product/en/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/en/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-GROUP.md @@ -44,7 +44,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-ROLE.md b/product/en/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-ROLE.md index 685750ea9b88a01d68d7cad6deb5dd6ca2b323fa..539478ed5c81b28f21c454dcedef3a311eb76138 100644 --- a/product/en/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/en/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-ROLE.md @@ -50,7 +50,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v2.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/en/docs-mogdb/v2.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index 192d945106107cf9cb8530a6c4e99fad3c5c42d7..bd16552ae6f24c377427ebc194c395ef228bdaa5 100644 --- a/product/en/docs-mogdb/v2.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/en/docs-mogdb/v2.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -13,7 +13,7 @@ The ODBC driver (psqlodbcw.so) provided by MogDB can be used after it has been c 1. Obtain the source code package of unixODBC by following link: - + [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) After the download, validate the integrity based on the integrity validation algorithm provided by the community. diff --git a/product/en/docs-mogdb/v2.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/en/docs-mogdb/v2.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 9fbe0358a7d1014e0e056247f870bfc0a219ea27..9c6208074ab3d891a13c7547b472a90ad0b0488a 100644 --- a/product/en/docs-mogdb/v2.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/en/docs-mogdb/v2.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -35,8 +35,6 @@ To measure the run time cost of each node in the execution plan, the current exe Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. -The **EXPLAIN PERFORMANCE** lightweight execution is consistent with **EXPLAIN PERFORMANCE** but greatly reduces the time spent on performance analysis. - ## Description As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail. diff --git a/product/en/docs-mogdb/v2.1/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md b/product/en/docs-mogdb/v2.1/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md index 827071a7debb1f54f9b8d19d7f1704d391041f02..a3604e1d540c78545f5451e62a1c971c6f92090a 100644 --- a/product/en/docs-mogdb/v2.1/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md +++ b/product/en/docs-mogdb/v2.1/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md @@ -64,7 +64,7 @@ Java 1.8.0_181 or later > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **Note:** > -> * Please refer to [https://www.java.com/en/download/help/path.html](https://www.java.com/en/download/help/path.html) to set the Java Home path. +> * Please refer to [java.com](https://www.java.com/en/download/help/path.html) to set the Java Home path. > * To ensure the optimal experience, the recommended minimum screen resolution is 1080 x 768. Below this resolution, the interface will be abnormal.
diff --git a/product/en/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-GROUP.md b/product/en/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-GROUP.md index 44a19a74bd4c3b3c62cf9d88eb8c2b97f3dba48a..dde0fcd1311a02259b49698a32c796d38a86926d 100644 --- a/product/en/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/en/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-GROUP.md @@ -44,7 +44,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-ROLE.md b/product/en/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-ROLE.md index 605202aaf64f7010ab45c4cd51992e5d2f6bff2d..6622f9bb7c59f319cbbacf9e5473ca9e962a2fc2 100644 --- a/product/en/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/en/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-ROLE.md @@ -50,7 +50,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index a5be42b5a6cfd6904af787b12d839298c5c9c180..0d14c66efcff16c8f3d9fca4988f1ff9de81500e 100644 --- a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -13,7 +13,7 @@ The ODBC driver (psqlodbcw.so) provided by MogDB can be used after it has been c 1. Obtain the source code package of unixODBC by following link: - + [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) After the download, validate the integrity based on the integrity validation algorithm provided by the community. diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 9fbe0358a7d1014e0e056247f870bfc0a219ea27..9c6208074ab3d891a13c7547b472a90ad0b0488a 100644 --- a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -35,8 +35,6 @@ To measure the run time cost of each node in the execution plan, the current exe Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. -The **EXPLAIN PERFORMANCE** lightweight execution is consistent with **EXPLAIN PERFORMANCE** but greatly reduces the time spent on performance analysis. - ## Description As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail. diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md index 827071a7debb1f54f9b8d19d7f1704d391041f02..a3604e1d540c78545f5451e62a1c971c6f92090a 100644 --- a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md +++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md @@ -64,7 +64,7 @@ Java 1.8.0_181 or later > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **Note:** > -> * Please refer to [https://www.java.com/en/download/help/path.html](https://www.java.com/en/download/help/path.html) to set the Java Home path. +> * Please refer to [java.com](https://www.java.com/en/download/help/path.html) to set the Java Home path. > * To ensure the optimal experience, the recommended minimum screen resolution is 1080 x 768. Below this resolution, the interface will be abnormal.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-GROUP.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-GROUP.md index 3c560ed5d05909da44847fd6ea27523906ff5959..275aed18665f73b7ec1fbbc3f05689f7cc656c42 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-GROUP.md @@ -48,7 +48,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-ROLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-ROLE.md index e4b9c79eef375ef2e06d64f7fd828b95876cf735..2aefd45bd38f343d7e5ccf694720f049899b9512 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-ROLE.md @@ -51,7 +51,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/unified-database-management-tool.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/unified-database-management-tool.md index f7b31057844923aa0161fbab5d7952071a003dfe..fb930696d99ae48871a17f7396a60e7ae8c947a6 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/unified-database-management-tool.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/unified-database-management-tool.md @@ -1483,7 +1483,7 @@ You can view cm_agent parameters in the `cm_agent.conf` file in the cm_agent dat **Value range**: Boolean values **on**, **off**, **true**, **false**, **yes**, **no**, **1**, and **0** The modification of this parameter takes effect after reloading. For details about how to modify the parameter, see [Parameters for set cm](#table9). -**Default value**: **on** +**Default value**: **off** #### datastorage_threshold_check_interval diff --git a/product/en/docs-mogdb/v3.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/en/docs-mogdb/v3.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index bf99262e288452354534795f9302e78462cc9252..b3eb23f8e8affff65d85a738bdfbb4b95da775f0 100644 --- a/product/en/docs-mogdb/v3.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/en/docs-mogdb/v3.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -13,7 +13,7 @@ The ODBC driver (psqlodbcw.so) provided by MogDB can be used after it has been c 1. Obtain the source code package of unixODBC by following link: - + [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) After the download, validate the integrity based on the integrity validation algorithm provided by the community. diff --git a/product/en/docs-mogdb/v3.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/en/docs-mogdb/v3.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 9fbe0358a7d1014e0e056247f870bfc0a219ea27..9c6208074ab3d891a13c7547b472a90ad0b0488a 100644 --- a/product/en/docs-mogdb/v3.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/en/docs-mogdb/v3.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -35,8 +35,6 @@ To measure the run time cost of each node in the execution plan, the current exe Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. -The **EXPLAIN PERFORMANCE** lightweight execution is consistent with **EXPLAIN PERFORMANCE** but greatly reduces the time spent on performance analysis. - ## Description As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail. diff --git a/product/en/docs-mogdb/v3.1/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md b/product/en/docs-mogdb/v3.1/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md index 827071a7debb1f54f9b8d19d7f1704d391041f02..a3604e1d540c78545f5451e62a1c971c6f92090a 100644 --- a/product/en/docs-mogdb/v3.1/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md +++ b/product/en/docs-mogdb/v3.1/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md @@ -64,7 +64,7 @@ Java 1.8.0_181 or later > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **Note:** > -> * Please refer to [https://www.java.com/en/download/help/path.html](https://www.java.com/en/download/help/path.html) to set the Java Home path. +> * Please refer to [java.com](https://www.java.com/en/download/help/path.html) to set the Java Home path. > * To ensure the optimal experience, the recommended minimum screen resolution is 1080 x 768. Below this resolution, the interface will be abnormal.
diff --git a/product/en/docs-mogdb/v3.1/reference-guide/guc-parameters/cm-parameters/cm_server.md b/product/en/docs-mogdb/v3.1/reference-guide/guc-parameters/cm-parameters/cm_server.md index 6b020d0a2067a44aa5cf472db9c5b3d7c774ddca..94445c42a29499438e15c5b69a97c8ad8df1ec68 100644 --- a/product/en/docs-mogdb/v3.1/reference-guide/guc-parameters/cm-parameters/cm_server.md +++ b/product/en/docs-mogdb/v3.1/reference-guide/guc-parameters/cm-parameters/cm_server.md @@ -96,7 +96,7 @@ date: 2022-05-23 **Value range**: Boolean. The value can be on, off, true, false, yes, no, 1, and 0. For parameter modification, see [Table 2 Methods for setting GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Default value**: **on** +**Default value**: **off** ## datastorage_threshold_check_interval diff --git a/product/en/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-GROUP.md b/product/en/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-GROUP.md index 3c560ed5d05909da44847fd6ea27523906ff5959..275aed18665f73b7ec1fbbc3f05689f7cc656c42 100644 --- a/product/en/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/en/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-GROUP.md @@ -48,7 +48,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-ROLE.md b/product/en/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-ROLE.md index e5c74a4820626b7981edf4b01f4f936a713cae26..64489b187641a3ddd696ecf2f794d1c2238e0103 100644 --- a/product/en/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/en/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-ROLE.md @@ -53,7 +53,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v3.1/reference-guide/tool-reference/unified-database-management-tool/introduction-to-cm-configuration-parameter.md b/product/en/docs-mogdb/v3.1/reference-guide/tool-reference/unified-database-management-tool/introduction-to-cm-configuration-parameter.md index 88e7aab15df0bd3f4f04f7ffae8583e514068730..bb04dfa39dda03eb945f1836daa8f3eff0cb6f51 100644 --- a/product/en/docs-mogdb/v3.1/reference-guide/tool-reference/unified-database-management-tool/introduction-to-cm-configuration-parameter.md +++ b/product/en/docs-mogdb/v3.1/reference-guide/tool-reference/unified-database-management-tool/introduction-to-cm-configuration-parameter.md @@ -458,7 +458,7 @@ You can view cm_agent parameters in the `cm_agent.conf` file in the cm_agent dat **Value range**: Boolean values **on**, **off**, **true**, **false**, **yes**, **no**, **1**, and **0** The modification of this parameter takes effect after reloading. For details about how to modify the parameter, see [Parameters for set cm](introduction-to-cm_ctl.md). -**Default value**: **on** +**Default value**: **off** ### datastorage_threshold_check_interval diff --git a/product/en/docs-mogdb/v5.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/en/docs-mogdb/v5.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index 69a32f00a505375f92c855930fbc6e74fb3054a4..6038f7ae2954afa26fb1688264ee52b6b2f65eac 100644 --- a/product/en/docs-mogdb/v5.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/en/docs-mogdb/v5.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -13,7 +13,7 @@ The ODBC driver (psqlodbcw.so) provided by MogDB can be used after it has been c 1. Obtain the source code package of unixODBC by following link: - + [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) After the download, validate the integrity based on the integrity validation algorithm provided by the community. diff --git a/product/en/docs-mogdb/v5.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md b/product/en/docs-mogdb/v5.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md index 493a43533e33f52bfd409cf9bad87ab2a07b6730..89a39d7611ad171f94eb06e7baa3e2096015db6e 100644 --- a/product/en/docs-mogdb/v5.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md +++ b/product/en/docs-mogdb/v5.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md @@ -197,7 +197,7 @@ Parameter description: Specifies the basic duration of cm_server arbitration del **Value range**: Boolean values **on**, **off**, **true**, **false**, **yes**, **no**, **1**, and **0** The modification of this parameter takes effect after reloading. For details, see [Options of set cm](./../introduction-to-cm_ctl-tool.md#setcm). -**Default value**: **on** +**Default value**: **off** ## datastorage_threshold_check_interval diff --git a/product/en/docs-mogdb/v5.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md b/product/en/docs-mogdb/v5.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md index 9fbe0358a7d1014e0e056247f870bfc0a219ea27..a5ab094453240ba707f990c48e99662d52c00662 100644 --- a/product/en/docs-mogdb/v5.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md +++ b/product/en/docs-mogdb/v5.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md @@ -1,136 +1,134 @@ ---- -title: Introduction to the SQL Execution Plan -summary: Introduction to the SQL Execution Plan -author: Guo Huan -date: 2021-03-16 ---- - -# Introduction to the SQL Execution Plan - -## Overview - -The SQL execution plan is a node tree, which displays detailed procedure when MogDB runs an SQL statement. A database operator indicates one step. - -You can run the **EXPLAIN** command to view the execution plan generated for each query by an optimizer. The output of **EXPLAIN** has one row for each execution node, showing the basic node type and the cost estimation that the optimizer made for the execution of this node, as shown in Figure 1. - -**Figure 1** SQL execution plan example - -![sql-execution-plan-example](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-1.png) - -- Nodes at the bottom level are scan nodes. They scan tables and return raw rows. The types of scan nodes (sequential scans and index scans) vary depending on the table access methods. Objects scanned by the bottom layer nodes may not be row-store data (not directly read from a table), such as **VALUES** clauses and functions that return rows, which have their own types of scan nodes. - -- If the query requires join, aggregation, sorting, or other operations on the raw rows, there will be other nodes above the scan nodes to perform these operations. In addition, there is more than one way to perform these operations, so different types of execution nodes may be displayed here. - -- The first row (the upper-layer node) estimates the total execution cost of the execution plan. Such an estimate indicates the value that the optimizer tries to minimize. - -### Execution Plan Information - -In addition to setting different display formats for an execution plan, you can use different **EXPLAIN** syntax to display execution plan information in detail. The following lists the common **EXPLAIN** syntax. For details about more **EXPLAIN** syntax, see EXPLAIN. - -- EXPLAIN **statement**: only generates an execution plan and does not execute. The *statement* indicates SQL statements. -- EXPLAIN ANALYZE **statement**: generates and executes an execution plan, and displays the execution summary. Then actual execution time statistics are added to the display, including the total elapsed time expended within each plan node (in milliseconds) and the total number of rows it actually returned. -- EXPLAIN PERFORMANCE **statement**: generates and executes the execution plan, and displays all execution information. - -To measure the run time cost of each node in the execution plan, the current execution of **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** adds profiling overhead to query execution. Running **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** on a query sometimes takes longer time than executing the query normally. The amount of overhead depends on the nature of the query, as well as the platform being used. - -Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. - -The **EXPLAIN PERFORMANCE** lightweight execution is consistent with **EXPLAIN PERFORMANCE** but greatly reduces the time spent on performance analysis. - -## Description - -As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail. - -### Execution Plans - -The following SQL statement is used as an example: - -```sql -SELECT * FROM t1, t2 WHERE t1.c1 = t2.c2; -``` - -Run the **EXPLAIN** command and the output is as follows: - -![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-2.png) - -**Interpretation of the execution plan level (vertical)**: - -1. Layer 1:**Seq Scan on t2** - - The table scan operator scans the table **t2** using **Seq Scan**. At this layer, data in the table **t2** is read from a buffer or disk, and then transferred to the upper-layer node for calculation. - -2. Layer 2:**Hash** - - Hash operator. It is used to calculate the hash value of the operator transferred from the lower layer for subsequent hash join operations. - -3. Layer 3:**Seq Scan on t1** - - The table scan operator scans the table **t1** using **Seq Scan**. At this layer, data in the table **t1** is read from a buffer or disk, and then transferred to the upper-layer node for hash join calculation. - -4. Layer 4:**Hash Join** - - Join operator. It is used to join data in the **t1** and **t2** tables using the hash join method and output the result data. - -**Keywords in the execution plan**: - -1. Table access modes - - - Seq Scan - - Scans all rows of the table in sequence. - - - Index Scan - - The optimizer uses a two-step plan: the child plan node visits an index to find the locations of rows matching the index condition, and then the upper plan node actually fetches those rows from the table itself. Fetching rows separately is much more expensive than reading them sequentially, but because not all pages of the table have to be visited, this is still cheaper than a sequential scan. The upper-layer planning node sorts index-identified rows based on their physical locations before reading them. This minimizes the independent capturing overhead. - - If there are separate indexes on multiple columns referenced in **WHERE**, the optimizer might choose to use an **AND** or **OR** combination of the indexes. However, this requires the visiting of both indexes, so it is not necessarily a win compared to using just one index and treating the other condition as a filter. - - The following Index scans featured with different sorting mechanisms are involved: - - - Bitmap Index Scan - - Fetches data pages using a bitmap. - - - Index Scan using index_name - - Fetches table rows in index order, which makes them even more expensive to read. However, there are so few rows that the extra cost of sorting the row locations is unnecessary. This plan type is used mainly for queries fetching just a single row and queries having an **ORDER BY** condition that matches the index order, because no extra sorting step is needed to satisfy **ORDER BY**. - -2. Table connection modes - - - Nested Loop - - A nested loop is used for queries that have a smaller data set connected. In a nested loop join, the foreign table drives the internal table and each row returned from the foreign table should have a matching row in the internal table. The returned result set of all queries should be less than 10,000. The table that returns a smaller subset will work as a foreign table, and indexes are recommended for connection columns of the internal table. - - - (Sonic) Hash Join - - A hash join is used for large tables. The optimizer uses a hash join, in which rows of one table are entered into an in-memory hash table, after which the other table is scanned and the hash table is probed for matches to each row. Sonic and non-Sonic hash joins differ in their hash table structures, which do not affect the execution result set. - - - Merge Join - - In most cases, the execution performance of a merge join is lower than that of a hash join. However, if the source data has been pre-sorted and no more sorting is needed during the merge join, its performance excels. - -3. Operators - - - sort - - Sorts the result set. - - - filter - - The **EXPLAIN** output shows the **WHERE** clause being applied as a **Filter** condition attached to the **Seq Scan** plan node. This means that the plan node checks the condition for each row it scans, and returns only the ones that meet the condition. The estimated number of output rows has been reduced because of the **WHERE** clause. However, the scan will still have to visit all 10,000 rows, as a result, the cost is not decreased. It increases a bit (by 10,000 x **cpu_operator_cost**) to reflect the extra CPU time spent on checking the **WHERE** condition. - - - LIMIT - - Limits the number of output execution results. If a **LIMIT** condition is added, not all rows are retrieved. - -### Execution Information - -The following SQL statement is used as an example: - -```sql -select sum(t2.c1) from t1,t2 where t1.c1=t2.c2 group by t1.c2; -``` - -The output of running **EXPLAIN PERFORMANCE** is as follows: - -![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-3.png) +--- +title: Introduction to the SQL Execution Plan +summary: Introduction to the SQL Execution Plan +author: Guo Huan +date: 2021-03-16 +--- + +# Introduction to the SQL Execution Plan + +## Overview + +The SQL execution plan is a node tree, which displays detailed procedure when MogDB runs an SQL statement. A database operator indicates one step. + +You can run the **EXPLAIN** command to view the execution plan generated for each query by an optimizer. The output of **EXPLAIN** has one row for each execution node, showing the basic node type and the cost estimation that the optimizer made for the execution of this node, as shown in Figure 1. + +**Figure 1** SQL execution plan example + +![sql-execution-plan-example](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-1.png) + +- Nodes at the bottom level are scan nodes. They scan tables and return raw rows. The types of scan nodes (sequential scans and index scans) vary depending on the table access methods. Objects scanned by the bottom layer nodes may not be row-store data (not directly read from a table), such as **VALUES** clauses and functions that return rows, which have their own types of scan nodes. + +- If the query requires join, aggregation, sorting, or other operations on the raw rows, there will be other nodes above the scan nodes to perform these operations. In addition, there is more than one way to perform these operations, so different types of execution nodes may be displayed here. + +- The first row (the upper-layer node) estimates the total execution cost of the execution plan. Such an estimate indicates the value that the optimizer tries to minimize. + +### Execution Plan Information + +In addition to setting different display formats for an execution plan, you can use different **EXPLAIN** syntax to display execution plan information in detail. The following lists the common **EXPLAIN** syntax. For details about more **EXPLAIN** syntax, see EXPLAIN. + +- EXPLAIN **statement**: only generates an execution plan and does not execute. The *statement* indicates SQL statements. +- EXPLAIN ANALYZE **statement**: generates and executes an execution plan, and displays the execution summary. Then actual execution time statistics are added to the display, including the total elapsed time expended within each plan node (in milliseconds) and the total number of rows it actually returned. +- EXPLAIN PERFORMANCE **statement**: generates and executes the execution plan, and displays all execution information. + +To measure the run time cost of each node in the execution plan, the current execution of **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** adds profiling overhead to query execution. Running **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** on a query sometimes takes longer time than executing the query normally. The amount of overhead depends on the nature of the query, as well as the platform being used. + +Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. + +## Description + +As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail. + +### Execution Plans + +The following SQL statement is used as an example: + +```sql +SELECT * FROM t1, t2 WHERE t1.c1 = t2.c2; +``` + +Run the **EXPLAIN** command and the output is as follows: + +![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-2.png) + +**Interpretation of the execution plan level (vertical)**: + +1. Layer 1:**Seq Scan on t2** + + The table scan operator scans the table **t2** using **Seq Scan**. At this layer, data in the table **t2** is read from a buffer or disk, and then transferred to the upper-layer node for calculation. + +2. Layer 2:**Hash** + + Hash operator. It is used to calculate the hash value of the operator transferred from the lower layer for subsequent hash join operations. + +3. Layer 3:**Seq Scan on t1** + + The table scan operator scans the table **t1** using **Seq Scan**. At this layer, data in the table **t1** is read from a buffer or disk, and then transferred to the upper-layer node for hash join calculation. + +4. Layer 4:**Hash Join** + + Join operator. It is used to join data in the **t1** and **t2** tables using the hash join method and output the result data. + +**Keywords in the execution plan**: + +1. Table access modes + + - Seq Scan + + Scans all rows of the table in sequence. + + - Index Scan + + The optimizer uses a two-step plan: the child plan node visits an index to find the locations of rows matching the index condition, and then the upper plan node actually fetches those rows from the table itself. Fetching rows separately is much more expensive than reading them sequentially, but because not all pages of the table have to be visited, this is still cheaper than a sequential scan. The upper-layer planning node sorts index-identified rows based on their physical locations before reading them. This minimizes the independent capturing overhead. + + If there are separate indexes on multiple columns referenced in **WHERE**, the optimizer might choose to use an **AND** or **OR** combination of the indexes. However, this requires the visiting of both indexes, so it is not necessarily a win compared to using just one index and treating the other condition as a filter. + + The following Index scans featured with different sorting mechanisms are involved: + + - Bitmap Index Scan + + Fetches data pages using a bitmap. + + - Index Scan using index_name + + Fetches table rows in index order, which makes them even more expensive to read. However, there are so few rows that the extra cost of sorting the row locations is unnecessary. This plan type is used mainly for queries fetching just a single row and queries having an **ORDER BY** condition that matches the index order, because no extra sorting step is needed to satisfy **ORDER BY**. + +2. Table connection modes + + - Nested Loop + + A nested loop is used for queries that have a smaller data set connected. In a nested loop join, the foreign table drives the internal table and each row returned from the foreign table should have a matching row in the internal table. The returned result set of all queries should be less than 10,000. The table that returns a smaller subset will work as a foreign table, and indexes are recommended for connection columns of the internal table. + + - (Sonic) Hash Join + + A hash join is used for large tables. The optimizer uses a hash join, in which rows of one table are entered into an in-memory hash table, after which the other table is scanned and the hash table is probed for matches to each row. Sonic and non-Sonic hash joins differ in their hash table structures, which do not affect the execution result set. + + - Merge Join + + In most cases, the execution performance of a merge join is lower than that of a hash join. However, if the source data has been pre-sorted and no more sorting is needed during the merge join, its performance excels. + +3. Operators + + - sort + + Sorts the result set. + + - filter + + The **EXPLAIN** output shows the **WHERE** clause being applied as a **Filter** condition attached to the **Seq Scan** plan node. This means that the plan node checks the condition for each row it scans, and returns only the ones that meet the condition. The estimated number of output rows has been reduced because of the **WHERE** clause. However, the scan will still have to visit all 10,000 rows, as a result, the cost is not decreased. It increases a bit (by 10,000 x **cpu_operator_cost**) to reflect the extra CPU time spent on checking the **WHERE** condition. + + - LIMIT + + Limits the number of output execution results. If a **LIMIT** condition is added, not all rows are retrieved. + +### Execution Information + +The following SQL statement is used as an example: + +```sql +select sum(t2.c1) from t1,t2 where t1.c1=t2.c2 group by t1.c2; +``` + +The output of running **EXPLAIN PERFORMANCE** is as follows: + +![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-3.png) diff --git a/product/en/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-GROUP.md b/product/en/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-GROUP.md index 3c560ed5d05909da44847fd6ea27523906ff5959..275aed18665f73b7ec1fbbc3f05689f7cc656c42 100644 --- a/product/en/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/en/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-GROUP.md @@ -48,7 +48,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-ROLE.md b/product/en/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-ROLE.md index e5c74a4820626b7981edf4b01f4f936a713cae26..64489b187641a3ddd696ecf2f794d1c2238e0103 100644 --- a/product/en/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/en/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-ROLE.md @@ -53,7 +53,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v5.2/characteristic-description/high-performance/1-cbo-optimizer.md b/product/en/docs-mogdb/v5.2/characteristic-description/high-performance/1-cbo-optimizer.md index 6db24fa092a86b4ce58bf8ed9cf89390fb5defed..089cd4b80eeb7136d47e6af02ac441499cf53d19 100644 --- a/product/en/docs-mogdb/v5.2/characteristic-description/high-performance/1-cbo-optimizer.md +++ b/product/en/docs-mogdb/v5.2/characteristic-description/high-performance/1-cbo-optimizer.md @@ -33,8 +33,4 @@ None ## Dependencies -None - -## Related Pages - -[Optimizer](../../performance-tuning/sql-tuning/sql-tuning-optimizer.md) \ No newline at end of file +None \ No newline at end of file diff --git a/product/en/docs-mogdb/v5.2/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/en/docs-mogdb/v5.2/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index 69a32f00a505375f92c855930fbc6e74fb3054a4..6038f7ae2954afa26fb1688264ee52b6b2f65eac 100644 --- a/product/en/docs-mogdb/v5.2/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/en/docs-mogdb/v5.2/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -13,7 +13,7 @@ The ODBC driver (psqlodbcw.so) provided by MogDB can be used after it has been c 1. Obtain the source code package of unixODBC by following link: - + [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) After the download, validate the integrity based on the integrity validation algorithm provided by the community. diff --git a/product/en/docs-mogdb/v5.2/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md b/product/en/docs-mogdb/v5.2/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md index 493a43533e33f52bfd409cf9bad87ab2a07b6730..89a39d7611ad171f94eb06e7baa3e2096015db6e 100644 --- a/product/en/docs-mogdb/v5.2/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md +++ b/product/en/docs-mogdb/v5.2/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md @@ -197,7 +197,7 @@ Parameter description: Specifies the basic duration of cm_server arbitration del **Value range**: Boolean values **on**, **off**, **true**, **false**, **yes**, **no**, **1**, and **0** The modification of this parameter takes effect after reloading. For details, see [Options of set cm](./../introduction-to-cm_ctl-tool.md#setcm). -**Default value**: **on** +**Default value**: **off** ## datastorage_threshold_check_interval diff --git a/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md b/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md index 7d20f9ec27daff1df0201b3f23ea76c508a9edcc..a5ab094453240ba707f990c48e99662d52c00662 100644 --- a/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md +++ b/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md @@ -35,8 +35,6 @@ To measure the run time cost of each node in the execution plan, the current exe Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. -The **EXPLAIN PERFORMANCE** lightweight execution is consistent with **EXPLAIN PERFORMANCE** but greatly reduces the time spent on performance analysis. - ## Description As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail. diff --git a/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/sql-tuning-optimizer.md b/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/sql-tuning-optimizer.md deleted file mode 100644 index 7259af48988ab71e823075a3ab2e42b806f2ef3f..0000000000000000000000000000000000000000 --- a/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/sql-tuning-optimizer.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Optimizer -summary: Optimizer -author: zhang cuiping -date: 2023-08-11 ---- - -# Optimizer - -Optimizer aims to create an optimized execution plan. A certain SQL query (query tree) can be actually executed in multiple modes, in which the same result set will generate. If possible, a query optimizer may check each possible execution plan and finally choose the one run in highest peed. - -> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**Note**: In some cases, checking all possible execution modes of a query may cost much time and memory, especially for some queries in execution that involve a large number of connection operations. Optimizer is used to judge a proper query plan instead of an optimized query plan in proper time. - -An optimizer works with the data structure called paths. The data structure is a planned simplified version, including necessary information used for decisions making by an optimizer. After finding an economical path, it will make an integrated plan tree to pass it to an executor. It includes enough details, that is the plans to be executed, which can be read by the executor and run. In the following sections, the distinctions between paths and plans are ignored. - -## A Possible Plan Generated - -The optimizer generates a plan for each relation (table) that appears in the scan query. The possible plans are determined by indexes available for each relation. A sequential search is always possible once for a relation, so a sequential search plan is always created. Suppose there is an index defined on a relation (such as a BTree index) and a query contains the constraint `relation.attribute OPR constant`. If `relation.attribute` happens to match a keyword in a BTree index and `OPR` is one of the operators listed in the operator class of the index, then another plan will be created that scans the relation using the B-tree index. If there are other indexes, and the constraints in the query match the keywords in that index, more plans will be generated. - -If the query asks to link two or more relations, the plan for the linked relation will not be considered until all feasible plans have been found while scanning a single relation. There are three possible join strategies: - -- Nested loop join: The right relation is scanned once for each row found in the left relation. This strategy is easy to implement, but can be time-consuming. However, if the right relation can be scanned with an index, then this might be a good strategy. The index scan of the right relation can be performed using the number from the current row of the left relation as the key. -- Merge join: Before the join starts, each relation sorts the join fields. The two relations are then scanned concurrently, and the matching rows are combined to form the join row. This union is more attractive because each relation is scanned only once. The required sorting step can be done either by an explicit sorting step or by scanning the relations in the appropriate order using the index on the join key. -- Hash join: First the right relation is scanned and loaded into a Hash table with the joined field as a hash key, then the left relation is scanned and each row found is used as a hash key to locate the matching row in the table. - -If there are more than two relations in a query, the final result must be built through a tree of join steps, each with two inputs. The optimizer examines the possible join orders and finds the one with the least cost. - -If the query uses fewer relations than geqo_threshold, a near-exhaustive search is run in order to find the best access sequence. The planner will prefer to connect between any two relationships that have a corresponding entry clause in the `WHERE` qualification (eg. there is a relationship like `where rel1.attr1=rel2.attr2`). Consider joining only when there is no other choices. There is no join clause for a particular relation, that is, no join clause is available for another relation. The planner thinks of all possible plans for each joining pair, and one of the criteria for choosing a plan is (presumably) to choose the cheapest one. - -The finished query tree consists of a sequential or index scan of the underlying relation, plus nested loop, merge, and hash join nodes as needed, plus any auxiliary steps needed, such as sort nodes or aggregate function calculation nodes. Most of these planning node types have additional *selection* (discard rows that don't match a specified boolean condition) and *projection* (compute a derived set of fields based on the given field values, that is to compute a scalar expression if needed). One responsibility of the optimizer is to attach a selection condition from the `WHERE` clause and the output expression needed to compute the most appropriate node for the plan tree. \ No newline at end of file diff --git a/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/sql-tuning.md b/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/sql-tuning.md index 773873207e299bf9ac59644c2d193bec230d6985..7690c5a268f239d9ea7acab501d6952687b523a6 100644 --- a/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/sql-tuning.md +++ b/product/en/docs-mogdb/v5.2/performance-tuning/sql-tuning/sql-tuning.md @@ -7,7 +7,6 @@ date: 2023-08-11 # SQL Optimization -- **[Optimizer](sql-tuning-optimizer.md)** - **[Query Execution Process](query-execution-process.md)** - **[Introduction to the SQL Execution Plan](introduction-to-the-sql-execution-plan.md)** - **[Tuning Process](tuning-process.md)** diff --git a/product/en/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-GROUP.md b/product/en/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-GROUP.md index 3c560ed5d05909da44847fd6ea27523906ff5959..275aed18665f73b7ec1fbbc3f05689f7cc656c42 100644 --- a/product/en/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/en/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-GROUP.md @@ -48,7 +48,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-ROLE.md b/product/en/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-ROLE.md index e5c74a4820626b7981edf4b01f4f936a713cae26..64489b187641a3ddd696ecf2f794d1c2238e0103 100644 --- a/product/en/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/en/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-ROLE.md @@ -53,7 +53,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v5.2/toc.md b/product/en/docs-mogdb/v5.2/toc.md index 7aedd1a18adf31c08893196503564e615891652e..8fb38145004bacbd2f6c5c84ce921fd295876d4c 100644 --- a/product/en/docs-mogdb/v5.2/toc.md +++ b/product/en/docs-mogdb/v5.2/toc.md @@ -729,7 +729,6 @@ + [Setting a Cgroup](./performance-tuning/system-tuning/resource-load-management/resource-management-preparations/setting-control-group.md) + [Creating a Resource Pool](/performance-tuning/system-tuning/resource-load-management/resource-management-preparations/creating-resource-pool.md) + [SQL Optimization](/performance-tuning/sql-tuning/sql-tuning.md) - + [Optimizer]( ./performance-tuning/sql-tuning/sql-tuning-optimizer.md) + [Query Execution Process](/performance-tuning/sql-tuning/query-execution-process.md) + [Introduction to the SQL Execution Plan](/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md) + [Tuning Process](/performance-tuning/sql-tuning/tuning-process.md) diff --git a/product/en/docs-mogdb/v5.2/toc_performance.md b/product/en/docs-mogdb/v5.2/toc_performance.md index 131fca458b91b75f7da70b0077ff8595a5da3f76..c5195ad597b3f1aaeec04c8a365370f3a164c675 100644 --- a/product/en/docs-mogdb/v5.2/toc_performance.md +++ b/product/en/docs-mogdb/v5.2/toc_performance.md @@ -18,7 +18,6 @@ + [Setting a Cgroup](/performance-tuning/system-tuning/resource-load-management/resource-management-preparations/setting-control-group.md) + [Creating a Resource Pool](/performance-tuning/system-tuning/resource-load-management/resource-management-preparations/creating-resource-pool.md) + [SQL Optimization](/performance-tuning/sql-tuning/sql-tuning.md) - + [Optimizer]( ./performance-tuning/sql-tuning/sql-tuning-optimizer.md) + [Query Execution Process](/performance-tuning/sql-tuning/query-execution-process.md) + [Introduction to the SQL Execution Plan](/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md) + [Tuning Process](/performance-tuning/sql-tuning/tuning-process.md) diff --git a/product/en/docs-mogdb/v6.0/characteristic-description/high-performance/1-cbo-optimizer.md b/product/en/docs-mogdb/v6.0/characteristic-description/high-performance/1-cbo-optimizer.md index 6db24fa092a86b4ce58bf8ed9cf89390fb5defed..089cd4b80eeb7136d47e6af02ac441499cf53d19 100644 --- a/product/en/docs-mogdb/v6.0/characteristic-description/high-performance/1-cbo-optimizer.md +++ b/product/en/docs-mogdb/v6.0/characteristic-description/high-performance/1-cbo-optimizer.md @@ -33,8 +33,4 @@ None ## Dependencies -None - -## Related Pages - -[Optimizer](../../performance-tuning/sql-tuning/sql-tuning-optimizer.md) \ No newline at end of file +None \ No newline at end of file diff --git a/product/en/docs-mogdb/v6.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/en/docs-mogdb/v6.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index 69a32f00a505375f92c855930fbc6e74fb3054a4..6038f7ae2954afa26fb1688264ee52b6b2f65eac 100644 --- a/product/en/docs-mogdb/v6.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/en/docs-mogdb/v6.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -13,7 +13,7 @@ The ODBC driver (psqlodbcw.so) provided by MogDB can be used after it has been c 1. Obtain the source code package of unixODBC by following link: - + [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) After the download, validate the integrity based on the integrity validation algorithm provided by the community. diff --git a/product/en/docs-mogdb/v6.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md b/product/en/docs-mogdb/v6.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md index 493a43533e33f52bfd409cf9bad87ab2a07b6730..89a39d7611ad171f94eb06e7baa3e2096015db6e 100644 --- a/product/en/docs-mogdb/v6.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md +++ b/product/en/docs-mogdb/v6.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md @@ -197,7 +197,7 @@ Parameter description: Specifies the basic duration of cm_server arbitration del **Value range**: Boolean values **on**, **off**, **true**, **false**, **yes**, **no**, **1**, and **0** The modification of this parameter takes effect after reloading. For details, see [Options of set cm](./../introduction-to-cm_ctl-tool.md#setcm). -**Default value**: **on** +**Default value**: **off** ## datastorage_threshold_check_interval diff --git a/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md b/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md index 7d20f9ec27daff1df0201b3f23ea76c508a9edcc..a5ab094453240ba707f990c48e99662d52c00662 100644 --- a/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md +++ b/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md @@ -35,8 +35,6 @@ To measure the run time cost of each node in the execution plan, the current exe Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. -The **EXPLAIN PERFORMANCE** lightweight execution is consistent with **EXPLAIN PERFORMANCE** but greatly reduces the time spent on performance analysis. - ## Description As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail. diff --git a/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/sql-tuning-optimizer.md b/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/sql-tuning-optimizer.md deleted file mode 100644 index 7259af48988ab71e823075a3ab2e42b806f2ef3f..0000000000000000000000000000000000000000 --- a/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/sql-tuning-optimizer.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Optimizer -summary: Optimizer -author: zhang cuiping -date: 2023-08-11 ---- - -# Optimizer - -Optimizer aims to create an optimized execution plan. A certain SQL query (query tree) can be actually executed in multiple modes, in which the same result set will generate. If possible, a query optimizer may check each possible execution plan and finally choose the one run in highest peed. - -> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**Note**: In some cases, checking all possible execution modes of a query may cost much time and memory, especially for some queries in execution that involve a large number of connection operations. Optimizer is used to judge a proper query plan instead of an optimized query plan in proper time. - -An optimizer works with the data structure called paths. The data structure is a planned simplified version, including necessary information used for decisions making by an optimizer. After finding an economical path, it will make an integrated plan tree to pass it to an executor. It includes enough details, that is the plans to be executed, which can be read by the executor and run. In the following sections, the distinctions between paths and plans are ignored. - -## A Possible Plan Generated - -The optimizer generates a plan for each relation (table) that appears in the scan query. The possible plans are determined by indexes available for each relation. A sequential search is always possible once for a relation, so a sequential search plan is always created. Suppose there is an index defined on a relation (such as a BTree index) and a query contains the constraint `relation.attribute OPR constant`. If `relation.attribute` happens to match a keyword in a BTree index and `OPR` is one of the operators listed in the operator class of the index, then another plan will be created that scans the relation using the B-tree index. If there are other indexes, and the constraints in the query match the keywords in that index, more plans will be generated. - -If the query asks to link two or more relations, the plan for the linked relation will not be considered until all feasible plans have been found while scanning a single relation. There are three possible join strategies: - -- Nested loop join: The right relation is scanned once for each row found in the left relation. This strategy is easy to implement, but can be time-consuming. However, if the right relation can be scanned with an index, then this might be a good strategy. The index scan of the right relation can be performed using the number from the current row of the left relation as the key. -- Merge join: Before the join starts, each relation sorts the join fields. The two relations are then scanned concurrently, and the matching rows are combined to form the join row. This union is more attractive because each relation is scanned only once. The required sorting step can be done either by an explicit sorting step or by scanning the relations in the appropriate order using the index on the join key. -- Hash join: First the right relation is scanned and loaded into a Hash table with the joined field as a hash key, then the left relation is scanned and each row found is used as a hash key to locate the matching row in the table. - -If there are more than two relations in a query, the final result must be built through a tree of join steps, each with two inputs. The optimizer examines the possible join orders and finds the one with the least cost. - -If the query uses fewer relations than geqo_threshold, a near-exhaustive search is run in order to find the best access sequence. The planner will prefer to connect between any two relationships that have a corresponding entry clause in the `WHERE` qualification (eg. there is a relationship like `where rel1.attr1=rel2.attr2`). Consider joining only when there is no other choices. There is no join clause for a particular relation, that is, no join clause is available for another relation. The planner thinks of all possible plans for each joining pair, and one of the criteria for choosing a plan is (presumably) to choose the cheapest one. - -The finished query tree consists of a sequential or index scan of the underlying relation, plus nested loop, merge, and hash join nodes as needed, plus any auxiliary steps needed, such as sort nodes or aggregate function calculation nodes. Most of these planning node types have additional *selection* (discard rows that don't match a specified boolean condition) and *projection* (compute a derived set of fields based on the given field values, that is to compute a scalar expression if needed). One responsibility of the optimizer is to attach a selection condition from the `WHERE` clause and the output expression needed to compute the most appropriate node for the plan tree. \ No newline at end of file diff --git a/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/sql-tuning.md b/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/sql-tuning.md index 773873207e299bf9ac59644c2d193bec230d6985..7690c5a268f239d9ea7acab501d6952687b523a6 100644 --- a/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/sql-tuning.md +++ b/product/en/docs-mogdb/v6.0/performance-tuning/sql-tuning/sql-tuning.md @@ -7,7 +7,6 @@ date: 2023-08-11 # SQL Optimization -- **[Optimizer](sql-tuning-optimizer.md)** - **[Query Execution Process](query-execution-process.md)** - **[Introduction to the SQL Execution Plan](introduction-to-the-sql-execution-plan.md)** - **[Tuning Process](tuning-process.md)** diff --git a/product/en/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-GROUP.md b/product/en/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-GROUP.md index 3c560ed5d05909da44847fd6ea27523906ff5959..275aed18665f73b7ec1fbbc3f05689f7cc656c42 100644 --- a/product/en/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/en/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-GROUP.md @@ -48,7 +48,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-ROLE.md b/product/en/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-ROLE.md index e5c74a4820626b7981edf4b01f4f936a713cae26..64489b187641a3ddd696ecf2f794d1c2238e0103 100644 --- a/product/en/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/en/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-ROLE.md @@ -53,7 +53,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/en/docs-mogdb/v6.0/toc.md b/product/en/docs-mogdb/v6.0/toc.md index 479033f5b103e08a760ccffc7fa13861ef300906..4a8e1315213ec850934628d82d897c9792c04c52 100644 --- a/product/en/docs-mogdb/v6.0/toc.md +++ b/product/en/docs-mogdb/v6.0/toc.md @@ -730,7 +730,6 @@ + [Setting a Cgroup](./performance-tuning/system-tuning/resource-load-management/resource-management-preparations/setting-control-group.md) + [Creating a Resource Pool](/performance-tuning/system-tuning/resource-load-management/resource-management-preparations/creating-resource-pool.md) + [SQL Optimization](/performance-tuning/sql-tuning/sql-tuning.md) - + [Optimizer]( ./performance-tuning/sql-tuning/sql-tuning-optimizer.md) + [Query Execution Process](/performance-tuning/sql-tuning/query-execution-process.md) + [Introduction to the SQL Execution Plan](/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md) + [Tuning Process](/performance-tuning/sql-tuning/tuning-process.md) diff --git a/product/en/docs-mogdb/v6.0/toc_performance.md b/product/en/docs-mogdb/v6.0/toc_performance.md index f1b70a71bb2cd9b7e2c96a7a71496b89c2124d7d..b22e367eaed5c570b11b09fd3b6856b073e1bc86 100644 --- a/product/en/docs-mogdb/v6.0/toc_performance.md +++ b/product/en/docs-mogdb/v6.0/toc_performance.md @@ -19,7 +19,6 @@ + [Setting a Cgroup](/performance-tuning/system-tuning/resource-load-management/resource-management-preparations/setting-control-group.md) + [Creating a Resource Pool](/performance-tuning/system-tuning/resource-load-management/resource-management-preparations/creating-resource-pool.md) + [SQL Optimization](/performance-tuning/sql-tuning/sql-tuning.md) - + [Optimizer]( ./performance-tuning/sql-tuning/sql-tuning-optimizer.md) + [Query Execution Process](/performance-tuning/sql-tuning/query-execution-process.md) + [Introduction to the SQL Execution Plan](/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md) + [Tuning Process](/performance-tuning/sql-tuning/tuning-process.md) diff --git a/product/zh/docs-mogdb/v1.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/zh/docs-mogdb/v1.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 8f013234c1b70776ce3ce92e81d2965a0de01a5d..f076080bf20e9b679e9d92b25b373f63fd637386 100644 --- a/product/zh/docs-mogdb/v1.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/zh/docs-mogdb/v1.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -37,8 +37,6 @@ SQL执行计划是一个节点树，显示openGauss执行一条SQL语句时执 因此，当定位SQL运行慢问题时，如果SQL长时间运行未结束，建议通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及其实际的运行信息，以便更精准地定位问题原因。 -EXPLAIN PERFORMANCE轻量化执行方式与EXPLAIN PERFORMANCE保持一致，在原来的基础上减少了性能分析的时间，执行时间与SQL执行时间的差异显著减少 -
## 详解 diff --git a/product/zh/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-GROUP.md b/product/zh/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-GROUP.md index eba311a8c20faf27201017d1c9f1fe2bbe5d3554..6a822bac739cf87bb1f6dc91ed4bc71f82a5fa76 100644 --- a/product/zh/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/zh/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-GROUP.md @@ -44,7 +44,7 @@ CREATE GROUP group_name [ [ WITH ] option [ ... ] ] [ ENCRYPTED | UNENCRYPTED ] | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-ROLE.md b/product/zh/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-ROLE.md index 9065d6c197f2fb918aa93a5d969e9947ea347efe..be7ce82b685dcbd1a934a9616c93df0a86f63f7e 100644 --- a/product/zh/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/zh/docs-mogdb/v1.1/reference-guide/sql-syntax/CREATE-ROLE.md @@ -50,7 +50,7 @@ CREATE ROLE role_name [ [ WITH ] option [ ... ] ] [ ENCRYPTED | UNENCRYPTED ] { | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v2.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/zh/docs-mogdb/v2.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index 3c79759b1ef803142370500ba53b10448312a3f3..1503b3261a4913faf561adee09104314ed5ffec7 100644 --- a/product/zh/docs-mogdb/v2.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/zh/docs-mogdb/v2.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -13,7 +13,11 @@ date: 2021-06-16 ## 操作步骤 -1. 获取unixODBC源码包。获取参考地址: 下载后请先按照社区提供的完整性校验算法进行完整性校验。 +1. 获取unixODBC源码包。获取参考地址: + + [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) + + 下载后请先按照社区提供的完整性校验算法进行完整性校验。 2. 安装unixODBC。如果机器上已经安装了其他版本的unixODBC，可以直接覆盖安装。 diff --git a/product/zh/docs-mogdb/v2.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/zh/docs-mogdb/v2.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 8f013234c1b70776ce3ce92e81d2965a0de01a5d..f076080bf20e9b679e9d92b25b373f63fd637386 100644 --- a/product/zh/docs-mogdb/v2.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/zh/docs-mogdb/v2.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -37,8 +37,6 @@ SQL执行计划是一个节点树，显示openGauss执行一条SQL语句时执 因此，当定位SQL运行慢问题时，如果SQL长时间运行未结束，建议通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及其实际的运行信息，以便更精准地定位问题原因。 -EXPLAIN PERFORMANCE轻量化执行方式与EXPLAIN PERFORMANCE保持一致，在原来的基础上减少了性能分析的时间，执行时间与SQL执行时间的差异显著减少 -
## 详解 diff --git a/product/zh/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-GROUP.md b/product/zh/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-GROUP.md index d18ba65dfef7bb1ce73e04a1a3295b8591a1d944..bddf36008f0a8531596e81f16e09ca23c6769827 100644 --- a/product/zh/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/zh/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-GROUP.md @@ -44,7 +44,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-ROLE.md b/product/zh/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-ROLE.md index 85e320ec1b036204bacaa506ebeaf27c789567ad..ac6925f7e652991748583ff061bb8a4b2ae3e0f1 100644 --- a/product/zh/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/zh/docs-mogdb/v2.0/reference-guide/sql-syntax/CREATE-ROLE.md @@ -50,7 +50,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v2.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/zh/docs-mogdb/v2.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index 60f50686aad0362c14cabd3396a4c903668fdf93..9185772bf624b7221fbcaff94ba5069f4f9909b4 100644 --- a/product/zh/docs-mogdb/v2.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/zh/docs-mogdb/v2.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -13,7 +13,11 @@ date: 2021-06-16 ## 操作步骤 -1. 获取unixODBC源码包。获取参考地址: 下载后请先按照社区提供的完整性校验算法进行完整性校验。 +1. 获取unixODBC源码包。 + + 获取参考地址: [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) + + 下载后请先按照社区提供的完整性校验算法进行完整性校验。 2. 安装unixODBC。如果机器上已经安装了其他版本的unixODBC，可以直接覆盖安装。 diff --git a/product/zh/docs-mogdb/v2.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/zh/docs-mogdb/v2.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 5c5e291abe7bf7f83a90d65004259fcfd2fe3d0c..ee04debe9634774a703ebbba91e5d625355a3f63 100644 --- a/product/zh/docs-mogdb/v2.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/zh/docs-mogdb/v2.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -37,8 +37,6 @@ SQL执行计划是一个节点树，显示openGauss执行一条SQL语句时执 因此，当定位SQL运行慢问题时，如果SQL长时间运行未结束，建议通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及其实际的运行信息，以便更精准地定位问题原因。 -EXPLAIN PERFORMANCE轻量化执行方式与EXPLAIN PERFORMANCE保持一致，在原来的基础上减少了性能分析的时间，执行时间与SQL执行时间的差异显著减少 -
## 详解 diff --git a/product/zh/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-GROUP.md b/product/zh/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-GROUP.md index 5c1c337e48343a6ebd820ae4b4822e7f41dc07f9..e7d9472f80e54e94e866a949440990684136ae03 100644 --- a/product/zh/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/zh/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-GROUP.md @@ -44,7 +44,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-ROLE.md b/product/zh/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-ROLE.md index 516d6ff56a69507fcd9e74aba76fa076ec3672fa..fdd9f28cfe998332152ecdace0ae34e83bd4e6c8 100644 --- a/product/zh/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/zh/docs-mogdb/v2.1/reference-guide/sql-syntax/CREATE-ROLE.md @@ -50,7 +50,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index cbe1bcae5497a8badea8abe9523412a6cbc4ec79..988606c742f7f379ba3a4a46c87b968b5e40e52d 100644 --- a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -15,7 +15,7 @@ date: 2021-06-16 1. 获取unixODBC源码包。 - 获取参考地址: + 获取参考地址: [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) 下载后请先按照社区提供的完整性校验算法进行完整性校验。 diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 4d83428d721bc09c853eb06e205924cadb90feba..b5716f2f23e9907eb87f04397948fb84d6abca6f 100644 --- a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -37,8 +37,6 @@ SQL执行计划是一个节点树，显示MogDB执行一条SQL语句时的详细 因此，当定位SQL运行慢问题时，如果SQL长时间运行未结束，建议通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及其实际的运行信息，以便更精准地定位问题原因。 -EXPLAIN PERFORMANCE轻量化执行方式与EXPLAIN PERFORMANCE保持一致，在原来的基础上减少了性能分析的时间，执行时间与SQL执行时间的差异显著减少 -
## 详解 diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md index 85bccf027bb0973d373acd5c78a7a223ded0e12c..37d2c287eaf44ba851265fd3cc9d34b6b32d0f44 100644 --- a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md +++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md @@ -129,11 +129,16 @@ date: 2021-04-20 | aformat_null_test | 控制rowtype类型判空逻辑,设置此项时，对于rowtype is not null判断，当一行数据有一列不为空的时候返回ture。否则，对于rowtype is not null判断，当一行数据所有列不为空的时候返回ture. | | aformat_regexp_match | 控制正则表达式函数的匹配行为。
设置此项，且sql_compatibility参数的值为A或B时，正则表达式的 flags 参数支持的选项含义有变更：
1. “.”默认不能匹配 '\n' 字符。
2. flags 中包含n选项时，“.”能够匹配 '\n' 字符。
3. regexp_replace(source, pattern replacement) 函数替换所有匹配的子串。
4. regexp_replace(source, pattern, replacement, flags) 在 flags值为” 或者null时，返回值为null。
否则，正则表达式的 flags 参数支持的选项含义：
1. “.”默认能匹配 '\n' 字符。
2. flags 中的 n 选项表示按照多行模式匹配。
3. regexp_replace(source, pattern replacement) 函数仅替换第一个匹配到的子串。
4. regexp_replace(source, pattern, replacement, flags) 在 flags值为” 或者null时，返回值为替换后的字符串。 | | compat_cursor | 控制隐式游标状态兼容行为。设置此项，且兼容O，隐式游标状态（SQL%FOUND、SQL%NOTFOUND、SQL%ISOPNE、SQL%ROWCOUNT）由原先的仅在当前执行的函数有效，拓展到包括本函数调用的子函数有效。 | -| proc_outparam_override | 控制存储过程出参的重载行为，打开该参数后，对于存储过程只有out出参部分不同的情况下，也可以正常调用。 | +| proc_outparam_override | 控制存储过程出参的重载行为，打开该参数后，对于存储过程只有out出参部分不同的情况下，也可以正常调用。设置此选项后，包含了out参数的函数或者存储过程，必须显式调用out参数。 | | proc_implicit_for_loop_variable | 控制存储过程中FOR_LOOP查询语句行为设置此项时，在FOR rec IN query LOOP语句中，若rec已经定义，不会复用已经定义的rec变量，而且重新建立一个新的变量。否则，会复用已经定义的rec变量，不会建立新的变量。 | | allow_procedure_compile_check | 控制存储过程中select语句和open cursor语句的编译检查设置此项时，在存储过程中执行select语句、open cursor for语句、cursor%rowtype语句、for rec in语句时，若查询的表不存在，则无法创建创建存储过程，不支持trigger函数的编译检查，若查询的表存在，则成功创建存储过程。 | | char_coerce_compat | 控制char(n)类型向其它变长字符串类型转换时的行为。默认情况下char(n)类型转换其它变长字符串类型时会省略尾部的空格，开启该参数后，转换时不再省略尾部的空格，并且在转换时如果char(n)类型的长度超过其它变长字符串类型时将会报错。该参数仅在sql_compatibility参数的值为A时生效。 | +> 关于proc_outparam_override选项和perform操作行为的说明如下： +> +> 1. 关闭proc_outparam_override选项时，针对out参数，perform不支持传入常量，必须传入变量；针对inout参数，perform支持传入常量，原因在于perform的作用是忽略out参数，此时给inout参数传常量，实际是给in参数传常量。 +> 2. 打开proc_outparam_override选项时，perform支持给out参数传入变量和常量，但是传入常量时会报错，原因在于out参数需要有变量来接收它的值，而传入常量时无法再给常量赋值，所以需要传变量。相当于打开此选项时，perform原本忽略out参数的特性不起作用。 + ## plpgsql.variable_conflict **参数说明**: 设置同名的存储过程变量和表的列的使用优先级。 diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-GROUP.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-GROUP.md index d54633231e3605630c1e77aafdecc56e8cdab550..7d7275e117e1fc20355dcbf65e0ee624e976ff92 100644 --- a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-GROUP.md @@ -48,7 +48,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-PROCEDURE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-PROCEDURE.md index 8e0f678ad14167333c031d723d70639388393223..0a5afe5b5dda64a2b7af1547fd6fc664049839a9 100644 --- a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-PROCEDURE.md +++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-PROCEDURE.md @@ -23,11 +23,11 @@ date: 2021-05-10 - 在存储过程内部调用其他有出参的函数，如果在赋值表达式中调用时，被调函数的出参可以省略，给出了也会被忽略。 - 存储过程支持参数注释的查看与导出、导入。 - 存储过程支持介于IS/AS与plsql_body之间的注释的查看与导出、导入。 -- 存储过程默认为SECURITY INVOKER权限，如果想将默认行为改为SECURITY DEFINER权限，需要设置guc参数behavior\_compat\_options='plsql\_security\_definer'。 +- 存储过程默认为SECURITY INVOKER权限，如果想将默认行为改为SECURITY DEFINER权限，需要设置guc参数behavior_compat_options='plsql_security_definer'。 - 被授予CREATE ANY FUNCTION权限的用户，可以在用户模式下创建/替换存储过程。 -- out/inout参数必须传入变量，不能够传入常量。 +- out/inout参数需要传入变量，不能为常量；关闭重载时，out参数在perform操作下可以不显式调用。关于proc_outparam_override选项和perform操作行为的详细说明参见[proc_outparam_override](../guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md#behavior_compat_options)。 - 创建存储过程时，若返回类型为游标，需注意out参数在前，in参数在后。 -- 集中式环境下，想要调用in参数相同，out参数不同的存储过程，需要设置guc参数behavior\_compat\_options='proc\_outparam\_override',并且打开参数后，无论使用select还是call调用存储过程，都必须加上out参数。打开参数后，不支持使用perform调用存储过程或函数。 +- 集中式环境下，想要调用in参数相同，out参数不同的存储过程，需要设置guc参数behavior_compat_options='proc_outparam_override',并且打开参数后，无论使用select还是call调用存储过程，都必须加上out参数。 ## 语法格式 diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-ROLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-ROLE.md index deaa9883c38b082e9a116b029fe6c8bdca3961ad..c1e020da6f56cc8643e287637b32d89ed108fb44 100644 --- a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/CREATE-ROLE.md @@ -51,7 +51,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/unified-database-management-tool.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/unified-database-management-tool.md index fcb9b87c8cf581f31e0a8ae9538ed47c15a45aa1..51ae72fa8db5385ba5d23c9da4a071dffbaad2e6 100644 --- a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/unified-database-management-tool.md +++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/unified-database-management-tool.md @@ -943,7 +943,7 @@ cm_agent相关参数可通过cm_agent数据目录下的cm_agent.conf文件查看 **取值范围**: 布尔型，有效值有on，off，true，false，yes，no，1，0。修改后可以reload生效，参数修改请参考[表 set cm参数](#table9)进行设置。 -**默认值**: on +**默认值**: off #### datastorage_threshold_check_interval diff --git a/product/zh/docs-mogdb/v3.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/zh/docs-mogdb/v3.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md index ff0c2438f67c80d0f69aaaed077b2a3996c137ba..3ffd336297262f521724e8d43ec586a15b90d1ae 100644 --- a/product/zh/docs-mogdb/v3.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md +++ b/product/zh/docs-mogdb/v3.1/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md @@ -15,7 +15,7 @@ date: 2021-06-16 1. 获取unixODBC源码包。 - 获取参考地址: + 获取参考地址: [https://sourceforge.net/projects/unixodbc/files/unixODBC](https://sourceforge.net/projects/unixodbc/files/unixODBC) 下载后请先按照社区提供的完整性校验算法进行完整性校验。 diff --git a/product/zh/docs-mogdb/v3.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/zh/docs-mogdb/v3.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md index 4d83428d721bc09c853eb06e205924cadb90feba..b5716f2f23e9907eb87f04397948fb84d6abca6f 100644 --- a/product/zh/docs-mogdb/v3.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md +++ b/product/zh/docs-mogdb/v3.1/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md @@ -37,8 +37,6 @@ SQL执行计划是一个节点树，显示MogDB执行一条SQL语句时的详细 因此，当定位SQL运行慢问题时，如果SQL长时间运行未结束，建议通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及其实际的运行信息，以便更精准地定位问题原因。 -EXPLAIN PERFORMANCE轻量化执行方式与EXPLAIN PERFORMANCE保持一致，在原来的基础上减少了性能分析的时间，执行时间与SQL执行时间的差异显著减少 -
## 详解 diff --git a/product/zh/docs-mogdb/v3.1/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md b/product/zh/docs-mogdb/v3.1/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md index 1bf3e95c52e24d21770f70378e7da8f850640dd2..a7990715d20844458ac2f2258dd5a493c0cbd273 100644 --- a/product/zh/docs-mogdb/v3.1/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md +++ b/product/zh/docs-mogdb/v3.1/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md @@ -140,12 +140,17 @@ date: 2021-04-20 | aformat_null_test | 控制rowtype类型判空逻辑,设置此项时，对于rowtype is not null判断，当一行数据有一列不为空的时候返回ture。否则，对于rowtype is not null判断，当一行数据所有列不为空的时候返回ture. | | aformat_regexp_match | 控制正则表达式函数的匹配行为。
设置此项，且sql_compatibility参数的值为A或B时，正则表达式的 flags 参数支持的选项含义有变更：
1. “.”默认不能匹配 '\n' 字符。
2. flags 中包含n选项时，“.”能够匹配 '\n' 字符。
3. regexp_replace(source, pattern replacement) 函数替换所有匹配的子串。
4. regexp_replace(source, pattern, replacement, flags) 在 flags值为” 或者null时，返回值为null。
否则，正则表达式的 flags 参数支持的选项含义：
1. “.”默认能匹配 '\n' 字符。
2. flags 中的 n 选项表示按照多行模式匹配。
3. regexp_replace(source, pattern replacement) 函数仅替换第一个匹配到的子串。
4. regexp_replace(source, pattern, replacement, flags) 在 flags值为” 或者null时，返回值为替换后的字符串。 | | compat_cursor | 控制隐式游标状态兼容行为。设置此项，且兼容O，隐式游标状态（SQL%FOUND、SQL%NOTFOUND、SQL%ISOPNE、SQL%ROWCOUNT）由原先的仅在当前执行的函数有效，拓展到包括本函数调用的子函数有效。 | -| proc_outparam_override | 控制存储过程出参的重载行为，打开该参数后，对于存储过程只有out出参部分不同的情况下，也可以正常调用。 | +| proc_outparam_override | 控制存储过程出参的重载行为，打开该参数后，对于存储过程只有out出参部分不同的情况下，也可以正常调用。设置此选项后，包含了out参数的函数或者存储过程，必须显式调用out参数。 | | proc_implicit_for_loop_variable | 控制存储过程中FOR_LOOP查询语句行为设置此项时，在FOR rec IN query LOOP语句中，若rec已经定义，不会复用已经定义的rec变量，而且重新建立一个新的变量。否则，会复用已经定义的rec变量，不会建立新的变量。 | | allow_procedure_compile_check | 控制存储过程中select语句和open cursor语句的编译检查设置此项时，在存储过程中执行select语句、open cursor for语句、cursor%rowtype语句、for rec in语句时，若查询的表不存在，则无法创建创建存储过程，不支持trigger函数的编译检查，若查询的表存在，则成功创建存储过程。 | | char_coerce_compat | 控制char(n)类型向其它变长字符串类型转换时的行为。默认情况下char(n)类型转换其它变长字符串类型时会省略尾部的空格，开启该参数后，转换时不再省略尾部的空格，并且在转换时如果char(n)类型的长度超过其它变长字符串类型时将会报错。该参数仅在sql_compatibility参数的值为A时生效。 | | pgformat_substr | 控制substr(str, from, for)在不同场景下的表现。默认情况下，当from小于0时，substr将从字符串尾部开始计数；当for小于1时，substr将返回NULL。开启该参数后，当from小于0时，将从字符串的第一位的前(-from + 1)位开始计数；当for小于0时，substr将报错。该参数仅在sql_compatibility参数的值为PG时生效。 | +> 关于proc_outparam_override选项和perform操作行为的说明如下： +> +> 1. 关闭proc_outparam_override选项时，针对out参数，perform不支持传入常量，必须传入变量；针对inout参数，perform支持传入常量，原因在于perform的作用是忽略out参数，此时给inout参数传常量，实际是给in参数传常量。 +> 2. 打开proc_outparam_override选项时，perform支持给out参数传入变量和常量，但是传入常量时会报错，原因在于out参数需要有变量来接收它的值，而传入常量时无法再给常量赋值，所以需要传变量。相当于打开此选项时，perform原本忽略out参数的特性不起作用。 + ## plpgsql.variable_conflict **参数说明**: 设置同名的存储过程变量和表的列的使用优先级。 diff --git a/product/zh/docs-mogdb/v3.1/reference-guide/guc-parameters/cm-parameters/cm_server.md b/product/zh/docs-mogdb/v3.1/reference-guide/guc-parameters/cm-parameters/cm_server.md index 9226d84f100c78b33c82f3e59b283ecf4970f7cf..9b7633a5aaefa4594430c87493a153d8e2848d8c 100644 --- a/product/zh/docs-mogdb/v3.1/reference-guide/guc-parameters/cm-parameters/cm_server.md +++ b/product/zh/docs-mogdb/v3.1/reference-guide/guc-parameters/cm-parameters/cm_server.md @@ -96,7 +96,7 @@ date: 2022-05-23 **取值范围**: 布尔型，有效值有on，off，true，false，yes，no，1，0。参数修改请参考[GUC参数设置方式](../../../reference-guide/guc-parameters/30-appendix.md)进行设置。 -**默认值**: on +**默认值**: off ## datastorage_threshold_check_interval diff --git a/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-GROUP.md b/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-GROUP.md index d54633231e3605630c1e77aafdecc56e8cdab550..7d7275e117e1fc20355dcbf65e0ee624e976ff92 100644 --- a/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-GROUP.md @@ -48,7 +48,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-PROCEDURE.md b/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-PROCEDURE.md index a5747a1d62c35f54eda0b72de036cda9c1044610..51673f0f10c114db4fa65fe5a3945e88cd7209db 100644 --- a/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-PROCEDURE.md +++ b/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-PROCEDURE.md @@ -23,11 +23,11 @@ date: 2021-05-10 - 在存储过程内部调用其他有出参的函数，如果在赋值表达式中调用时，被调函数的出参可以省略，给出了也会被忽略。 - 存储过程支持参数注释的查看与导出、导入。 - 存储过程支持介于IS/AS与plsql_body之间的注释的查看与导出、导入。 -- 存储过程默认为SECURITY INVOKER权限，如果想将默认行为改为SECURITY DEFINER权限，需要设置guc参数behavior\_compat\_options='plsql\_security\_definer'。 +- 存储过程默认为SECURITY INVOKER权限，如果想将默认行为改为SECURITY DEFINER权限，需要设置guc参数behavior_compat_options='plsql_security_definer'。 - 被授予CREATE ANY FUNCTION权限的用户，可以在用户模式下创建/替换存储过程。 -- out/inout参数必须传入变量，不能够传入常量。 +- out/inout参数需要传入变量，不能为常量；关闭重载时，out参数在perform操作下可以不显式调用。关于proc_outparam_override选项和perform操作行为的详细说明参见[proc_outparam_override](../guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md#behavior_compat_options)。 - 创建存储过程时，若返回类型为游标，需注意out参数在前，in参数在后。 -- 集中式环境下，想要调用in参数相同，out参数不同的存储过程，需要设置guc参数behavior\_compat\_options='proc\_outparam\_override',并且打开参数后，无论使用select还是call调用存储过程，都必须加上out参数。打开参数后，不支持使用perform调用存储过程或函数。 +- 集中式环境下，想要调用in参数相同，out参数不同的存储过程，需要设置guc参数behavior_compat_options='proc_outparam_override',并且打开参数后，无论使用select还是call调用存储过程，都必须加上out参数。 ## 语法格式 diff --git a/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-ROLE.md b/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-ROLE.md index 77370929c8c3727d1909171a30611b9a38d749b7..6c7a9418c130774c5af9f8152e0474993340e66a 100644 --- a/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/zh/docs-mogdb/v3.1/reference-guide/sql-syntax/CREATE-ROLE.md @@ -53,7 +53,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v3.1/reference-guide/tool-reference/unified-database-management-tool/introduction-to-cm-configuration-parameter.md b/product/zh/docs-mogdb/v3.1/reference-guide/tool-reference/unified-database-management-tool/introduction-to-cm-configuration-parameter.md index b3768cacac5359ccad47bb8d9ea96a4e2eb492bf..479312cf717fe716bd73140bf25557d042d01c28 100644 --- a/product/zh/docs-mogdb/v3.1/reference-guide/tool-reference/unified-database-management-tool/introduction-to-cm-configuration-parameter.md +++ b/product/zh/docs-mogdb/v3.1/reference-guide/tool-reference/unified-database-management-tool/introduction-to-cm-configuration-parameter.md @@ -458,7 +458,7 @@ cm_agent相关参数可通过cm_agent数据目录下的cm_agent.conf文件查看 **取值范围**: 布尔型，有效值有on，off，true，false，yes，no，1，0。修改后可以reload生效，参数修改请参考[cm_ctl工具介绍#表 set cm参数](introduction-to-cm_ctl.md)进行设置。 -**默认值**: on +**默认值**: off ### datastorage_threshold_check_interval diff --git a/product/zh/docs-mogdb/v5.0/characteristic-description/high-performance/1-cbo-optimizer.md b/product/zh/docs-mogdb/v5.0/characteristic-description/high-performance/1-cbo-optimizer.md index aaa8461875a01ad2650b876950051a36c7b10830..a907ed92de4324aa0349635202d56d0d6dec0e17 100644 --- a/product/zh/docs-mogdb/v5.0/characteristic-description/high-performance/1-cbo-optimizer.md +++ b/product/zh/docs-mogdb/v5.0/characteristic-description/high-performance/1-cbo-optimizer.md @@ -33,8 +33,4 @@ MogDB CBO优化器能够在众多计划中依据代价选出最高效的执行 ## 依赖关系 -无。 - -## 相关页面 - -[优化器](../../performance-tuning/sql-tuning/sql-tuning-optimizer.md) \ No newline at end of file +无。 \ No newline at end of file diff --git a/product/zh/docs-mogdb/v5.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md b/product/zh/docs-mogdb/v5.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md index 8724ead3378540caaa0d517ea13adcce3b4b7932..edcbfc84b491cce1289b769fa3e93f06e5130334 100644 --- a/product/zh/docs-mogdb/v5.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md +++ b/product/zh/docs-mogdb/v5.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md @@ -197,7 +197,7 @@ date: 2023-04-07 **取值范围**：布尔型，有效值有on，off，true，false，yes，no，1，0。修改后可以reload生效，参数修改请参考[表 set cm参数](./../introduction-to-cm_ctl-tool.md#setcm)进行设置。 -**默认值**：on +**默认值**：off ## datastorage_threshold_check_interval diff --git a/product/zh/docs-mogdb/v5.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md b/product/zh/docs-mogdb/v5.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md index fb75822537f107d6c437584e5bee8103eb488375..1b811eeb1d31d8214aa64500db22a87018a6430f 100644 --- a/product/zh/docs-mogdb/v5.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md +++ b/product/zh/docs-mogdb/v5.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md @@ -37,8 +37,6 @@ SQL执行计划是一个节点树，显示MogDB执行一条SQL语句时的详细 因此，当定位SQL运行慢问题时，如果SQL长时间运行未结束，建议通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及其实际的运行信息，以便更精准地定位问题原因。 -EXPLAIN PERFORMANCE轻量化执行方式与EXPLAIN PERFORMANCE保持一致，在原来的基础上减少了性能分析的时间，执行时间与SQL执行时间的差异显著减少 -
## 详解 diff --git a/product/zh/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-GROUP.md b/product/zh/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-GROUP.md index 88f34d5afe7946a764c3cf90f9b06f8d7944f666..2343f01dc6cc46541d58161bf13e6050320d1a64 100644 --- a/product/zh/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/zh/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-GROUP.md @@ -49,7 +49,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-ROLE.md b/product/zh/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-ROLE.md index 6463393ff9cf1c65e8b9495750f6836391add61b..0f186b1b755cfbadce521b766ea0babf71765b49 100644 --- a/product/zh/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/zh/docs-mogdb/v5.0/reference-guide/sql-syntax/CREATE-ROLE.md @@ -54,7 +54,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v5.2/characteristic-description/high-performance/1-cbo-optimizer.md b/product/zh/docs-mogdb/v5.2/characteristic-description/high-performance/1-cbo-optimizer.md index aaa8461875a01ad2650b876950051a36c7b10830..a907ed92de4324aa0349635202d56d0d6dec0e17 100644 --- a/product/zh/docs-mogdb/v5.2/characteristic-description/high-performance/1-cbo-optimizer.md +++ b/product/zh/docs-mogdb/v5.2/characteristic-description/high-performance/1-cbo-optimizer.md @@ -33,8 +33,4 @@ MogDB CBO优化器能够在众多计划中依据代价选出最高效的执行 ## 依赖关系 -无。 - -## 相关页面 - -[优化器](../../performance-tuning/sql-tuning/sql-tuning-optimizer.md) \ No newline at end of file +无。 \ No newline at end of file diff --git a/product/zh/docs-mogdb/v5.2/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md b/product/zh/docs-mogdb/v5.2/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md index 8724ead3378540caaa0d517ea13adcce3b4b7932..edcbfc84b491cce1289b769fa3e93f06e5130334 100644 --- a/product/zh/docs-mogdb/v5.2/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md +++ b/product/zh/docs-mogdb/v5.2/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md @@ -197,7 +197,7 @@ date: 2023-04-07 **取值范围**：布尔型，有效值有on，off，true，false，yes，no，1，0。修改后可以reload生效，参数修改请参考[表 set cm参数](./../introduction-to-cm_ctl-tool.md#setcm)进行设置。 -**默认值**：on +**默认值**：off ## datastorage_threshold_check_interval diff --git a/product/zh/docs-mogdb/v5.2/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md b/product/zh/docs-mogdb/v5.2/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md index fb75822537f107d6c437584e5bee8103eb488375..1b811eeb1d31d8214aa64500db22a87018a6430f 100644 --- a/product/zh/docs-mogdb/v5.2/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md +++ b/product/zh/docs-mogdb/v5.2/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md @@ -37,8 +37,6 @@ SQL执行计划是一个节点树，显示MogDB执行一条SQL语句时的详细 因此，当定位SQL运行慢问题时，如果SQL长时间运行未结束，建议通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及其实际的运行信息，以便更精准地定位问题原因。 -EXPLAIN PERFORMANCE轻量化执行方式与EXPLAIN PERFORMANCE保持一致，在原来的基础上减少了性能分析的时间，执行时间与SQL执行时间的差异显著减少 -
## 详解 diff --git a/product/zh/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-GROUP.md b/product/zh/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-GROUP.md index 88f34d5afe7946a764c3cf90f9b06f8d7944f666..2343f01dc6cc46541d58161bf13e6050320d1a64 100644 --- a/product/zh/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/zh/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-GROUP.md @@ -49,7 +49,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-ROLE.md b/product/zh/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-ROLE.md index 6463393ff9cf1c65e8b9495750f6836391add61b..0f186b1b755cfbadce521b766ea0babf71765b49 100644 --- a/product/zh/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/zh/docs-mogdb/v5.2/reference-guide/sql-syntax/CREATE-ROLE.md @@ -54,7 +54,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v6.0/characteristic-description/high-performance/1-cbo-optimizer.md b/product/zh/docs-mogdb/v6.0/characteristic-description/high-performance/1-cbo-optimizer.md index aaa8461875a01ad2650b876950051a36c7b10830..a907ed92de4324aa0349635202d56d0d6dec0e17 100644 --- a/product/zh/docs-mogdb/v6.0/characteristic-description/high-performance/1-cbo-optimizer.md +++ b/product/zh/docs-mogdb/v6.0/characteristic-description/high-performance/1-cbo-optimizer.md @@ -33,8 +33,4 @@ MogDB CBO优化器能够在众多计划中依据代价选出最高效的执行 ## 依赖关系 -无。 - -## 相关页面 - -[优化器](../../performance-tuning/sql-tuning/sql-tuning-optimizer.md) \ No newline at end of file +无。 \ No newline at end of file diff --git a/product/zh/docs-mogdb/v6.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md b/product/zh/docs-mogdb/v6.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md index 87e23083319120b0524e7f2585426274e8869a87..16f64f286a7f6fc203995dc2ba5f5bb6e56e2200 100644 --- a/product/zh/docs-mogdb/v6.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md +++ b/product/zh/docs-mogdb/v6.0/high-available-guide/cluster-management/cm-configuration-parameter/cm-cm_server.md @@ -197,7 +197,7 @@ date: 2023-04-07 **取值范围**：布尔型，有效值有on，off，true，false，yes，no，1，0。修改后可以reload生效，参数修改请参考[表 set cm参数](./../introduction-to-cm_ctl-tool.md#setcm)进行设置。 -**默认值**：on +**默认值**：off ## datastorage_threshold_check_interval diff --git a/product/zh/docs-mogdb/v6.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md b/product/zh/docs-mogdb/v6.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md index fb75822537f107d6c437584e5bee8103eb488375..1b811eeb1d31d8214aa64500db22a87018a6430f 100644 --- a/product/zh/docs-mogdb/v6.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md +++ b/product/zh/docs-mogdb/v6.0/performance-tuning/sql-tuning/introduction-to-the-sql-execution-plan.md @@ -37,8 +37,6 @@ SQL执行计划是一个节点树，显示MogDB执行一条SQL语句时的详细 因此，当定位SQL运行慢问题时，如果SQL长时间运行未结束，建议通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及其实际的运行信息，以便更精准地定位问题原因。 -EXPLAIN PERFORMANCE轻量化执行方式与EXPLAIN PERFORMANCE保持一致，在原来的基础上减少了性能分析的时间，执行时间与SQL执行时间的差异显著减少 -
## 详解 diff --git a/product/zh/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-GROUP.md b/product/zh/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-GROUP.md index 88f34d5afe7946a764c3cf90f9b06f8d7944f666..2343f01dc6cc46541d58161bf13e6050320d1a64 100644 --- a/product/zh/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-GROUP.md +++ b/product/zh/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-GROUP.md @@ -49,7 +49,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-ROLE.md b/product/zh/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-ROLE.md index 76a318e738a442dcc41be1a2eea1da8fac08d854..4419e0e70e0387b94ff0bbd64833653fc0ca60fe 100644 --- a/product/zh/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-ROLE.md +++ b/product/zh/docs-mogdb/v6.0/reference-guide/sql-syntax/CREATE-ROLE.md @@ -54,7 +54,7 @@ option ::= {SYSADMIN | NOSYSADMIN} | IN ROLE role_name [, ...] | IN GROUP role_name [, ...] | ROLE role_name [, ...] - | ADMIN rol e_name [, ...] + | ADMIN role_name [, ...] | USER role_name [, ...] | SYSID uid | DEFAULT TABLESPACE tablespace_name diff --git a/product/zh/docs-zcloud-for-mogdb/v6.3/basic-features/tenant-proxy-nodes-management.md b/product/zh/docs-zcloud-for-mogdb/v6.3/basic-features/tenant-proxy-nodes-management.md index 78d4ccf75c36c6fa50583d4a46ede331e8e3f59b..876954321c80093abe3e7edc683440d3135d2b66 100644 --- a/product/zh/docs-zcloud-for-mogdb/v6.3/basic-features/tenant-proxy-nodes-management.md +++ b/product/zh/docs-zcloud-for-mogdb/v6.3/basic-features/tenant-proxy-nodes-management.md @@ -10,7 +10,7 @@ date: 2024-08-12 设置-->资源池管理-->Proxy节点管理 -![img](file:///C:\Users\Haruna\AppData\Local\Temp\ksohtml12624\wps115.jpg) +![img](https://cdn-mogdb.enmotech.com/docs-media/zcloud-for-mogdb/basic-features/basic-features-229.png) ## 功能说明 @@ -28,6 +28,6 @@ date: 2024-08-12 点击“部署”，选择“加入到已有的Proxy集群”，下拉选择要加入的Proxy。 -![img](file:///C:\Users\Haruna\AppData\Local\Temp\ksohtml12624\wps116.jpg) +![img](https://cdn-mogdb.enmotech.com/docs-media/zcloud-for-mogdb/basic-features/basic-features-230.png) 输入Proxy节点信息：IP地址、SSH端口、Proxy管理端口、服务器Root或者sudo 权限的用户、密码。