diff --git a/product/en/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md b/product/en/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md index f5cd1c17044b5c81819a0e4930c29f34693d04be..810d4da9452d2a0e2cd7478682c77b7242313aae 100644 --- a/product/en/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md +++ b/product/en/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md @@ -70,5 +70,3 @@ You are advised to use the default installation packages of the following depend | readline_devel | 7.0-13 | | openSSH | 8.4p1 | | expect | 5.45.4 | - -**NOTE**: Installation is supported even if there is only 4 GB memory in actual test. If the memory size is greater than 4 GB, it does not need to be modified. \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md index b514c4a570283baabfa7c770f411939b1f8c5380..e8a84ac49efebfb756d76ac5ca59580cc9ec713b 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md @@ -19,7 +19,7 @@ The valid values are **stderr**, **csvlog**, and **syslog**. - **stderr** indicates that logs are printed to the screen. -- **csvlog** indicates that logs are output in comma separated value (CSV) format. The prerequisite for generating logs in CSV format is that **[logging_collector](#logging_collector)** must be set to **on**. For details, see **Using CSV Log Output**. +- **csvlog** indicates that logs are output in comma separated value (CSV) format. The prerequisite for generating logs in CSV format is that [logging_collector](#logging_collector) must be set to **on**. For details, see [Using CSV Log Output](4-using-csv-log-output.md). - **syslog** indicates that logs are recorded using the syslog of the OS. MogDB can record logs using syslog from **LOCAL0** to **LOCAL7**. For details, see **[syslog_facility](#syslog_facility)**. To record logs using syslog, add the following information to syslog daemon's configuration file: diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md index ed8bb50f352511913951026463c4ff7354f0a0da..d69c1c7169da52c4c5fb4e94d7cfad41cfa17222 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md @@ -16,7 +16,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > A same value for **client_min_messages** and **[log_min_messages](#log_min_messages)** does not indicate the same level. -**Value range**: enumerated values. Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see **Table 1 Message severity levels**. If the configured level is higher than **error**, for example, **fatal** or **panic**, the system changes the level to **error** by default. +**Value range**: enumerated values. Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see Table 1 [Message severity levels](#Message severity levels). If the configured level is higher than **error**, for example, **fatal** or **panic**, the system changes the level to **error** by default. **Default value**: **notice** @@ -29,7 +29,7 @@ This parameter is a SUSET parameter. Set it based on instructions provided in Ta > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > A same value for **[client_min_messages](#client_min_messages)** and **log_min_messages** does not indicate the same level. -**Value range**: enumerated values. Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see **Table 1 Message severity levels**. +**Value range**: enumerated values. Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see Table 1 [Message severity levels](#Message severity levels). **Default value**: **warning** @@ -39,7 +39,7 @@ This parameter is a SUSET parameter. Set it based on instructions provided in Ta This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: enumerated values. Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see **Table 1 Message severity levels**. +**Value range**: enumerated values. Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see Table 1 [Message severity levels](#Message severity levels). > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** > @@ -57,7 +57,7 @@ Setting this parameter can be helpful in tracking down unoptimized queries. For This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** -> When using this option together with **log_statement**, the text of statements that are logged because of **log_statement** will not be repeated in the duration log message. If you are not using **syslog**, it is recommended that you log the process ID (PID) or session ID using **log_line_prefix** so that you can link the statement message to the later duration message. +> When using this option together with [log_statement](3-logging-content.md#log_statement), the text of statements that are logged because of **log_statement** will not be repeated in the duration log message. If you are not using **syslog**, it is recommended that you log the process ID (PID) or session ID using [log_line_prefix](3-logging-content.md#log_line_prefix) so that you can link the statement message to the later duration message. **Value range**: an integer ranging from -1 to *INT_MAX*. The unit is ms. @@ -78,7 +78,7 @@ This parameter is a SUSET parameter. Set it based on instructions provided in Ta **Value range**: enumerated values -Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see **Table 1 Message severity levels**. +Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see Table 1 [Message severity levels](#Message severity levels). **Default value**: **panic** diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md index 37a4cd43829e56ecaff833924d365c61861ca9b9..4940fe66f5ad3de6ace3df182777958e7d06c9b4 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md @@ -176,13 +176,13 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T | %S | session ID | | %% | The character % | -The %c escape character prints a unique session ID consisting of two 4-byte hexadecimal numbers separated by a period (.). The numbers are the process startup time and the process ID. Therefore, %c can also be used as a space saving way of printing those items. For example, run the following query to generate the session ID from **pg_stat_activity**: - -``` -SELECT to_hex(EXTRACT(EPOCH FROM backend_start)::integer) || '.' || - to_hex(pid) -FROM pg_stat_activity; -``` +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The %c escape character prints a unique session ID consisting of two 4-byte hexadecimal numbers separated by a period (.). The numbers are the process startup time and the process ID. Therefore, %c can also be used as a space saving way of printing those items. For example, run the following query to generate the session ID from **pg_stat_activity**: +> +> ```sql +> SELECT to_hex(EXTRACT(EPOCH FROM backend_start)::integer) || '.' || +> to_hex(pid) +> FROM pg_stat_activity; +> ``` - If you set a nonempty value for **log_line_prefix**, you should usually make its last character be a space, to provide visual separation from the rest of the log line. A punctuation character can be used, too. - Syslog generates its own time stamp and process ID information. Therefore, you do not need to include those escapes characters when you are logging in to syslog. @@ -198,7 +198,7 @@ FROM pg_stat_activity; ## log_lock_waits -**Parameter description**: If the time for which a session waits to acquire a lock is longer than the value of **deadlock_timeout**, this parameter specifies whether to record this message in the database. This is useful in determining if lock waits are causing poor performance. +**Parameter description**: If the time for which a session waits to acquire a lock is longer than the value of [deadlock_timeout](../../../reference-guide/guc-parameters/16-lock-management.md#deadlock_timeout), this parameter specifies whether to record this message in the database. This is useful in determining if lock waits are causing poor performance. This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). @@ -243,11 +243,11 @@ This parameter is a SUSET parameter. Set it based on instructions provided in Ta ## log_timezone -**Parameter description**: Specifies the time zone used for timestamps written in the server log. Different from **TimeZone**, this parameter takes effect for all sessions in the database. +**Parameter description**: Specifies the time zone used for timestamps written in the server log. Different from [TimeZone](../../../reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md#timezone), this parameter takes effect for all sessions in the database. This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: a string +**Value range**: a string. You can obtain it by querying the PG\_TIMEZONE\_NAMES view. **Default value**: **PRC** @@ -262,12 +262,12 @@ This parameter is a USERSET parameter. Set it based on instructions provided in **Value range**: a string -**Default value**: **off**. All the module logs are not output on the server. You can view the logs by running **show logging_module**. Example modules are displayed as follows: ALL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,OPFUSION,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT). +**Default value**: **off**. All the module logs are not output on the server. You can view the logs by running **show logging\_module**. Example modules are displayed as follows: ALL,on\(\),off\(DFS,GUC,ORC,SLRU,MEM\_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,OPFUSION,VEC\_EXECUTOR,LLVM,OPT,OPT\_REWRITE,OPT\_JOIN,OPT\_AGG,OPT\_SUBPLAN,OPT\_SETOP,OPT\_SKEW,UDF,COOP\_ANALYZE,WLMCP,ACCELERATE,,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN\_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE\_CKPT,DBL\_WRT,RTO,HEARTBEAT\). **Setting method**: Run **show logging_module** to view which modules are controllable. For example, the query output result is as follows: -``` -mogdb=# show logging_module; +```sql +MogDB=# show logging_module; logging_module -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ALL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,T,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT) @@ -276,10 +276,10 @@ ALL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR Controllable modules are identified by uppercase letters, and the special ID **ALL** is used for setting all module logs. You can control the output of module logs by setting **logging_module** to **on** or **off**. Enable log output for SSL: -``` -mogdb=# set logging_module='on(SSL)'; +```sql +MogDB=# set logging_module='on(SSL)'; SET -mogdb=# show logging_module; logging_module +MogDB=# show logging_module; logging_module ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ALL,on(SSL),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT,COMM_IPC,COMM_PARAM) (1 row) ``` @@ -288,16 +288,16 @@ SSL log output is enabled. The **ALL** identifier can be used to quickly enable or disable log output for all modules. -``` -mogdb=# set logging_module='off(ALL)'; +```sql +MogDB=# set logging_module='off(ALL)'; SET -mogdb=# show logging_module; logging_module +MogDB=# show logging_module; logging_module -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ALL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT) (1 row) -mogdb=# set logging_module='on(ALL)'; +MogDB=# set logging_module='on(ALL)'; SET -mogdb=# show logging_module; logging_module +MogDB=# show logging_module; logging_module -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ALL,on(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT),off() (1 row) ``` diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md index 4d77a6529893242f35107a51e7df0df8fdb0bc13..e902483500d2903f66a53c25f24d7db37303f0de 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md @@ -9,8 +9,8 @@ date: 2021-04-20 **Prerequisites** -- The **log_destination** parameter is set to **csvlog**. -- The **logging_collector** parameter is set to **on**. +- The [log_destination](1-logging-destination.md#log_destination) parameter is set to **csvlog**. +- The [logging_collector](1-logging-destination.md#logging_collector) parameter is set to **on**. **Definition of csvlog** @@ -83,6 +83,6 @@ COPY gaussdb_log FROM '/opt/data/pg_log/logfile.csv' WITH csv; Simplify importing CSV log files by performing the following operations: -- Set **log_filename** and **log_rotation_age** to provide a consistent, predictable naming solution for log files. By doing this, you can predict when an individual log file is complete and ready to be imported. -- Set **log_rotation_size** to **0** to disable size-based log rollback, as it makes the log file name difficult to predict. -- Set **log_truncate_on_rotation** to **on** so that old log data cannot be mixed with the new one in the same file. +- Set [log_filename](1-logging-destination.md#log_filename) and [log_rotation_age](1-logging-destination.md#log_rotation_age) to provide a consistent, predictable naming solution for log files. By doing this, you can predict when an individual log file is complete and ready to be imported. +- Set [log_rotation_size](1-logging-destination.md#log_rotation_size) to **0** to disable size-based log rollback, as it makes the log file name difficult to predict. +- Set [log_truncate_on_rotation](1-logging-destination.md#log_truncate_on_rotation) to **on** so that old log data cannot be mixed with the new one in the same file. diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md index 7d333ed2e6cb5bf9b23f219827a08a203f52e0db..2209191d932bd356b0375803c1eb6fd0d8fa126f 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md @@ -33,12 +33,12 @@ This parameter is a SUSET parameter. Set it based on instructions provided in Ta - **on** indicates that the statistics collection function is enabled. - **off** indicates that the statistics collection function is disabled. -> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** +**Default value**: **on** + +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**NOTE:** > > When the database to be cleaned up is selected from the AutoVacuum automatic cleanup process, the database statistics are required. In this case, the default value is set to **on**. -**Default value**: **on** - ## track_io_timing **Parameter description:** Collects statistics about I/O timing in the database. The I/O timing statistics can be queried by using the **pg_stat_database** parameter. @@ -121,6 +121,8 @@ This parameter is a USERSET parameter. Set it based on instructions provided in **Parameter description**: Collects statistics about the statements (**SELECT**, **INSERT**, **UPDATE**, **MERGE INTO**, and **DELETE**) that are being executed in a session. +In the x86-based centralized deployment scenario, the hardware configuration specifications are 32-core CPU and 256 GB memory. When the Benchmark SQL 5.0 tool is used to test performance, the performance fluctuates by about 0.8% by enabling or disabling this parameter. + This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). **Value range**: Boolean diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md index 14c370f85ba7ab356851b899f82b05eaf52e90e7..f41af5b4ded6d01c380d67e1989b3ecbd5103902 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md @@ -62,19 +62,6 @@ This parameter is a USERSET parameter. Set it based on instructions provided in **Default value**: empty -## default_storage_nodegroup - -**Parameter description**: Specifies the Node Group where a table is created by default. This parameter takes effect only for ordinary tables. - -This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -- **installation** indicates that tables will be created in the Node Group created during database installation. -- A value other than **installation** indicates that tables will be created in the Node Group specified by this parameter. - -**Value range**: a string - -**Default value**: **installation** - ## temp_tablespaces **Parameter description**: Specifies tablespaces to which temporary objects will be created (temporary tables and their indexes) when a CREATE command does not explicitly specify a tablespace. Temporary files for sorting large data are created in these tablespaces. @@ -180,7 +167,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** > Although you can set this parameter to a value ranging from 0 to 1000000000 anytime, VACUUM will limit the effective value to half the value of **autovacuum_freeze_max_age** by default. -**Default value**: **5000000000** +**Default value**: **2000000000** ## vacuum_freeze_table_age @@ -240,7 +227,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: an integer that is greater than or equal to 1 +**Value range**: an integer ranging from 1 to 2147483647 **Default value**: **1000** @@ -252,4 +239,4 @@ This parameter is a USERSET parameter. Set it based on instructions provided in **Valid value**: an integer. The minimum value is 64 and the maximum value is INT_MAX. The default unit is KB. -**Default value**: **4MB** +**Default value**: **4 MB** diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md index 92b7c55d5c1bb559e59b7a9d37216b8e7ff38cd7..6c9a4b40055ec2d06e43a037a24d0cd667756896 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md @@ -38,7 +38,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in - **postgres** indicates that output matching PostgreSQL 8.4 will be generated when the **[DateStyle](#DateStyle)** parameter is set to **ISO**. - **postgres_verbose** indicates that output matching PostgreSQL 8.4 will be generated when the **[DateStyle](#DateStyle)** parameter is set to **non_ISO**. - **iso_8601** indicates that output matching the time interval "format with designators" defined in ISO 8601 will be generated. -- **a** indicates the output result that matches the numtodsinterval function. For details, see numtodsinterval. +- **a** indicates the output result that matches the numtodsinterval function. For details, see [numtodsinterval](../../../reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md). > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > The IntervalStyle parameter also affects the interpretation of ambiguous interval input. diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md index 981e9481cc1b660bf15de020c09194f3dbe8bdf1..9b8e0a493a135570077db3d4e150eb6416aa5208 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md @@ -16,7 +16,7 @@ This section describes the default database loading parameters. The value of **dynamic_library_path** must be a list of absolute paths separated by colons (:). When the name of a path starts with the special variable \$libdir, the variable will be replaced with the directory in which the module provided by the MogDB is installed. For example: ```bash -dynamic_library_path = '/usr/local/lib/gaussdb:/opt/testgs/lib:$libdir' +dynamic_library_path = '/usr/local/lib/mogdb:/opt/testgs/lib:$libdir' ``` This parameter is a SUSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md index 383ab24742dfc8a0f2e14688e05bd44136d59195..60ff727224ba0909f0785c437bd32764910aa2d3 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md @@ -66,7 +66,7 @@ This parameter is a SUSET parameter. Set it based on instructions provided in Ta ## quote_all_identifiers -**Parameter description:** When the database generates SQL, this parameter forcibly quotes all identifiers even if they are not keywords. This will affect the output of EXPLAIN as well as the results of functions, such as pg_get_viewdef. For details, see the **-quote-all-identifiers** parameter of **gs_dump**. +**Parameter description:** When the database generates SQL, this parameter forcibly quotes all identifiers even if they are not keywords. This will affect the output of EXPLAIN as well as the results of functions, such as pg_get_viewdef. For details, see the **--quote-all-identifiers** parameter of **gs_dump**. This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). @@ -131,3 +131,18 @@ This parameter is a USERSET parameter. Set it based on instructions provided in - **off** indicates that the features are disabled. **Default value**: **off** + +## default_with_oids + +**Parameter description**: Specifies whether **CREATE TABLE** and **CREATE TABLE AS** include an **OID** field in newly-created tables if neither **WITH OIDS** nor **WITHOUT OIDS** is specified. It also determines whether OIDs will be included in tables created by **SELECT INTO**. + +It is not recommended that OIDs be used in user tables. Therefore, this parameter is set to **off** by default. When OIDs are required for a particular table, **WITH OIDS** needs to be specified during the table creation. + +This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: Boolean + +- **on** indicates that **CREATE TABLE** and **CREATE TABLE AS** can include an **OID** field in newly-created tables. +- **off** indicates that **CREATE TABLE** and **CREATE TABLE AS** cannot include any OID field in newly-created tables. + +**Default value**: **off** \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md index ab1ef65d5283b26573d07e2f82b845e72ecb511b..37c12d8c5577a9ad29efd7be3875189d76828d38 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md @@ -78,7 +78,9 @@ This parameter is a POSTMASTER parameter. Set it based on instructions provided ## sql_compatibility -**Parameter description**: Specifies the type of mainstream database with which the SQL syntax and statement behavior of the database is compatible. This parameter is an INTERNAL parameter. It can be viewed but cannot be modified. +**Parameter description**: Specifies the type of mainstream database with which the SQL syntax and statement behavior of the database is compatible. + +This parameter is an INTERNAL parameter. It can be viewed but cannot be modified. **Value range**: enumerated values @@ -91,7 +93,7 @@ This parameter is a POSTMASTER parameter. Set it based on instructions provided > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > -> - This parameter can be set only when you run the CREATE DATABASE command to create a database. +> - This parameter can be set only when you run the [CREATE DATABASE](../../../reference-guide/sql-syntax/CREATE-DATABASE.md) command to create a database. > - In the database, this parameter must be set to a specific value. It can be set to **A** or **B** and cannot be changed randomly. Otherwise, the setting is not consistent with the database behavior. ## behavior_compat_options @@ -111,19 +113,27 @@ This parameter is a USERSET parameter. Set it based on instructions provided in **Table 1** Compatibility configuration items -| Configuration Item | Behavior | -| :------------------------ | :----------------------------------------------------------- | -| display_leading_zero | Specifies how floating point numbers are displayed.
- If this item is not specified, for a decimal number between -1 and 1, the 0 before the decimal point is not displayed. For example, 0.25 is displayed as **.25**.
- If this item is specified, for a decimal number between -1 and 1, the 0 before the decimal point is displayed. For example, 0.25 is displayed as **0.25**. | -| end_month_calculate | Specifies the calculation logic of the add_months function.
Assume that the two parameters of the add_months function are **param1** and **param2**, and that the month of **param1** and **param2** is **result**.
- If this item is not specified, and the **Day** of **param1** indicates the last day of a month shorter than **result**, the **Day** in the calculation result will equal that in **param1**. For example:
`mogdb=# select add_months('2018-02-28',3) from sys_dummy; add_months ---------------------- 2018-05-28 00:00:00 (1 row)`
- If this item is specified, and the **Day** of **param1** indicates the last day of a month shorter than **result**, the **Day** in the calculation result will equal that in **result**. For example:
`mogdb=# select add_months('2018-02-28',3) from sys_dummy; add_months ---------------------- 2018-05-31 00:00:00 (1 row)` | -| compat_analyze_sample | Specifies the sampling behavior of the ANALYZE operation.
If this item is specified, the sample collected by the ANALYZE operation will be limited to around 30,000 records, DBnode memory consumption and maintaining the stability of ANALYZE. | -| bind_schema_tablespace | Binds a schema with the tablespace with the same name.
If a tablespace name is the same as *sche_name*, **default_tablespace** will also be set to *sche_name* if **search_path** is set to *sche_name*. | -| bind_procedure_searchpath | Specifies the search path of the database object for which no schema name is specified.
If no schema name is specified for a stored procedure, the search is performed in the schema to which the stored procedure belongs.
If the stored procedure is not found, the following operations are performed:
- If this item is not specified, the system reports an error and exits.
- If this item is specified, the search continues based on the settings of **search_path**. If the issue persists, the system reports an error and exits. | -| correct_to_number | Controls the compatibility of the to_number() result.
If this item is specified, the result of the to_number() function is the same as that of PG11. Otherwise, the result is the same as that of the O database. | -| unbind_dive_bound | Controls the range check on the result of integer division.
If this item is specified, you do not need to check the range of the division result. For example, the result of INT_MIN/(-1) can be *INT_MAX*+1. If this item is not specified, an out-of-bounds error is reported because the result is greater than*INT_MAX*. | -| return_null_string | Specifies how to display the empty result (empty string ") of the lpad() and rpad() functions.
- If this item is not specified, the empty string is displayed as **NULL**.
`mogdb=# select length(lpad('123',0,'*')) from sys_dummy; length ---- (1 row)`
- If this item is specified, the empty string is displayed as single quotation marks (").
`mogdb=# select length(lpad('123',0,'*')) from sys_dummy; length ---- 0 (1 row)` | -| compat_concat_variadic | Specifies the compatibility of variadic results of the concat() and concat_ws() functions.
If this item is specified and a concat function has a parameter of the variadic type, different result formats in O and Teradata are retained. If this item is not specified and a concat function has a parameter of the variadic type, the result format of O is retained for both O and Teradata. This option has no effect on MY because MY has no variadic type. | -| merge_update_multi | When MERGE INTO… WHEN MATCHED THEN UPDATE (see **MERGE INTO**) and INSERT… ON DUPLICATE KEY UPDATE (see **INSERT**) are used, control the UPDATE behavior if a piece of target data in the target table conflicts with multiple pieces of source data.
If this item is specified and the preceding scenario exists, the system performs multiple UPDATE operations on the conflicting row. If this item is not specified and the preceding scenario exists, an error is reported, that is, the MERGE or INSERT operation fails. | -| hide_tailing_zero | Numeric shows the configuration item. If this parameter is not set, numeric shows the configuration item based on the specified precision. When this parameter is set, hide "0" at the end of the decimal point.
`set behavior_compat_options='hide_tailing_zero'; select cast(123.123 as numeric(15,10)); numeric ---- 123.123 (1 row)` | +| Configuration Item | Behavior | +| :------------------------------ | :----------------------------------------------------------- | +| display_leading_zero | Specifies how floating point numbers are displayed.
- If this item is not specified, for a decimal number between -1 and 1, the 0 before the decimal point is not displayed. For example, 0.25 is displayed as **.25**.
- If this item is specified, for a decimal number between -1 and 1, the 0 before the decimal point is displayed. For example, 0.25 is displayed as **0.25**. | +| end_month_calculate | Specifies the calculation logic of the add_months function.
Assume that the two parameters of the add_months function are **param1** and **param2**, and that the month of **param1** and **param2** is **result**.
- If this item is not specified, and the **Day** of **param1** indicates the last day of a month shorter than **result**, the **Day** in the calculation result will equal that in **param1**. For example:
`mogdb=# select add_months('2018-02-28',3) from sys_dummy; add_months ---------------------- 2018-05-28 00:00:00 (1 row)`
- If this item is specified, and the **Day** of **param1** indicates the last day of a month shorter than **result**, the **Day** in the calculation result will equal that in **result**. For example:
`mogdb=# select add_months('2018-02-28',3) from sys_dummy; add_months ---------------------- 2018-05-31 00:00:00 (1 row)` | +| compat_analyze_sample | Specifies the sampling behavior of the ANALYZE operation.
If this item is specified, the sample collected by the ANALYZE operation will be limited to around 30,000 records, DBnode memory consumption and maintaining the stability of ANALYZE. | +| bind_schema_tablespace | Binds a schema with the tablespace with the same name.
If a tablespace name is the same as *sche_name*, **default_tablespace** will also be set to *sche_name* if **search_path** is set to *sche_name*. | +| bind_procedure_searchpath | Specifies the search path of the database object for which no schema name is specified.
If no schema name is specified for a stored procedure, the search is performed in the schema to which the stored procedure belongs.
If the stored procedure is not found, the following operations are performed:
- If this item is not specified, the system reports an error and exits.
- If this item is specified, the search continues based on the settings of **search_path**. If the issue persists, the system reports an error and exits. | +| correct_to_number | Controls the compatibility of the to_number() result.
If this item is specified, the result of the to_number() function is the same as that of PG11. Otherwise, the result is the same as that of the O database. | +| unbind_dive_bound | Controls the range check on the result of integer division.
If this item is specified, you do not need to check the range of the division result. For example, the result of INT_MIN/(-1) can be *INT_MAX*+1. If this item is not specified, an out-of-bounds error is reported because the result is greater than*INT_MAX*. | +| return_null_string | Specifies how to display the empty result (empty string ") of the lpad() and rpad() functions.
- If this item is not specified, the empty string is displayed as **NULL**.
`mogdb=# select length(lpad('123',0,'*')) from sys_dummy; length ---- (1 row)`
- If this item is specified, the empty string is displayed as single quotation marks (").
`mogdb=# select length(lpad('123',0,'*')) from sys_dummy; length ---- 0 (1 row)` | +| compat_concat_variadic | Specifies the compatibility of variadic results of the concat() and concat_ws() functions.
If this item is specified and a concat function has a parameter of the variadic type, different result formats in O and Teradata are retained. If this item is not specified and a concat function has a parameter of the variadic type, the result format of O is retained for both O and Teradata. This option has no effect on MY because MY has no variadic type. | +| merge_update_multi | When MERGE INTO… WHEN MATCHED THEN UPDATE (see **MERGE INTO**) and INSERT… ON DUPLICATE KEY UPDATE (see **INSERT**) are used, control the UPDATE behavior if a piece of target data in the target table conflicts with multiple pieces of source data.
If this item is specified and the preceding scenario exists, the system performs multiple UPDATE operations on the conflicting row. If this item is not specified and the preceding scenario exists, an error is reported, that is, the MERGE or INSERT operation fails. | +| hide_tailing_zero | Numeric shows the configuration item. If this parameter is not set, numeric shows the configuration item based on the specified precision. When this parameter is set, hide "0" at the end of the decimal point.
`set behavior_compat_options='hide_tailing_zero'; select cast(123.123 as numeric(15,10)); numeric ---- 123.123 (1 row)` | +| rownum_type_compat | Specifies the ROWNUM type. The default value is **INT8**. After this parameter is specified, the value is changed to **NUMERIC**. | +| aformat_null_test | Determines the logic for checking whether the row type is not null. When this parameter is set, if a column in a row is not null, **true** is returned.
When this parameter is not set, if all columns in a row are not null, **true** is returned. | +| aformat_regexp_match | Determines the matching behavior of regular expression functions.
When this parameter is set and **sql_compatibility** is set to **A** or **B**, the options supported by the **flags** parameter of the regular expression are changed as follows:
1. By default, the character '\n' cannot be matched.
2. When **flags** contains the **n** option, the character '\n' can be matched.
3. The **regexp_replace(source, pattern replacement)** function replaces all matching substrings.
4. **regexp_replace(source, pattern, replacement, flags)** returns null when the value of **flags** is **“** or null.
Otherwise, the meanings of the options supported by the **flags** parameter of the regular expression are as follows:
1. By default, the character '\n' can be matched.
2. The **n** option in **flags** indicates that the multi-line matching mode is used.
3. The **regexp_replace(source, pattern replacement)** function replaces only the first matched substring.
4. If the value of **flags** is **“** or null, the return value of **regexp_replace(source, pattern, replacement, flags)** is the character string after replacement. | +| compat_cursor | Determines the compatibility behavior of implicit cursor states. If this parameter is set and the O compatibility mode is used, the effective scope of implicit cursor states (**SQL %FOUND**, **SQL %NOTFOUND**, **SQL %ISOPNE** and **SQL %ROWCOUNT**) are extended only the currently executed function to all subfunctions invoked by this function. | +| proc_outparam_override | Determines the reloading of output parameters of a stored procedure. After this parameter is enabled, the stored procedure can be properly invoked even if only the output parameters of the stored procedure are different. | +| proc_implicit_for_loop_variable | Determines the behavior of the **FOR_LOOP** query statement in a stored procedure.When this parameter is set, if **rec** has been defined in the **FOR rec IN query LOOP** statement, the defined **rec** variable is not reused and a new variable is created. Otherwise, the defined **rec** variable is reused and no new variable is created. | +| allow_procedure_compile_check | Determines the compilation check of the **SELECT** and **OPEN CURSOR** statements in a stored procedure. If this parameter is set, when the **SELECT**, **OPEN CURSOR FOR**, **CURSOR %rowtype**, or **for rec in** statement is executed in a stored procedure, the stored procedure cannot be created if the queried table does not exist, and the compilation check of the trigger function is not supported. If the queried table exists, the stored procedure is successfully created. | +| char_coerce_compat | Determines the behavior when char(n) types are converted to other variable-length string types. By default, spaces at the end are omitted when the char(n) type is converted to other variable-length string types. After this parameter is enabled, spaces at the end are not omitted during conversion. In addition, if the length of the char(n) type exceeds the length of other variable-length string types, an error is reported. This parameter is valid only when **sql_compatibility** is set to **A**. | ## plpgsql.variable_conflict diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md index 97b8c94fc79a4d87c08f33934e0c9ac8e30a14c0..6bd63e365bc01d71b14fd6d62cd9e911670ff5c0 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md @@ -111,3 +111,15 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > Ensure that this parameter is set to **1048576**. Adjust this parameter only when required. Otherwise, **audit_resource_policy** may fail to take effect. To control the storage space and time of audit logs, set the **audit_resource_policy**, **audit_space_limit**, and **audit_file_remain_time** parameters. + +## audit_thread_num + +**Parameter description**: Specifies the number of audit threads. + +This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range:** an integer ranging from 1 to 48 + +**Default value**: **1** + +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** When **audit_dml_state** is enabled and high performance is required, you are advised to increase the value of this parameter to ensure that audit messages can be processed and recorded in a timely manner. \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md index 9a79cf6bb19a14e09970d5f2cff08ceac21dc59f..a4d75205699a634f66cd5c39d534bde0be9be171 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md @@ -13,14 +13,14 @@ date: 2021-04-20 This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: an integer ranging from 0 to 524287 +**Value range**: an integer ranging from 0 to 67108863 - **0** indicates that the function of auditing the CREATE, DROP, and ALTER operations on MogDB database objects is disabled. - Other values indicate that the CREATE, DROP, and ALTER operations on a certain or some MogDB database objects are audited. **Value description:** -The value of this parameter is calculated by 20 binary bits. The 20 binary bits represent 20 types of MogDB database objects. If the corresponding binary bit is set to **0**, the CREATE, DROP, and ALTER operations on corresponding database objects are not audited. If it is set to **1**, the CREATE, DROP, and ALTER operations are audited. For details about the audit contents represented by these 19 binary bits, see [Table 1](#audit_system_object). +The value of this parameter is calculated by 26 binary bits. The 26 binary bits represent 26 types of MogDB database objects. If the corresponding binary bit is set to **0**, the CREATE, DROP, and ALTER operations on corresponding database objects are not audited. If it is set to **1**, the CREATE, DROP, and ALTER operations are audited. For details about the audit contents represented by these 19 binary bits, see [Table 1](#audit_system_object). **Default value**: **12295** @@ -49,6 +49,11 @@ The value of this parameter is calculated by 20 binary bits. The 20 binary bits | Bit 18 | Whether to audit the CREATE, DROP, and ALTER operations on workloads. | **0** indicates that the CREATE, DROP, and ALTER operations on types are not audited.
**1** indicates that the CREATE, DROP, and ALTER operations on types are audited. | | Bit 19 | Whether to audit the CREATE, DROP, and ALTER operations on sequences. | **0** indicates that the operations are not audited.
**1** indicates that the operations are audited. | | Bit 20 | Whether to audit the CREATE and DROP operations on CMK and CEK objects. | **0** indicates that the CREATE and DROP operations on CMK and CEK objects are not audited.
**1** indicates that the CREATE and DROP operations on CMK and CEK objects are audited. | +| Bit 21 | Whether to audit the CREATE, DROP, and ALTER operations on PACKAGE objects. | **0** indicates that the operations are not audited.
**1** indicates that the operations are audited. | +| Bit 22 | Whether to audit the CREATE and DROP operations on MODEL objects. | **0** indicates that the CREATE and ALTER operations are not audited.
**1** indicates that the CREATE and DROP operations are audited. | +| Bit 23 | Whether to audit the CREATE, DROP, and ALTER operations on PUBLICATION and SUBSCRIPTION objects. | **0** indicates that the CREATE, DROP, and ALTER operations are not audited.
**1** indicates that the CREATE, DROP, and ALTER operations are audited. | +| Bit 24 | Whether to audit the ALTER and DROP operations on the **gs_global_config** objects. | **0** indicates that the ALTER and DROP operations are not audited.
**1** indicates that the ALTER and DROP operations are audited. | +| Bit 25 | Whether to audit the CREATE, DROP, and ALTER operations on FOREIGN DATA WRAPPER objects. | **0** indicates that the CREATE, DROP, and ALTER operations are not audited.
**1** indicates that the CREATE, DROP, and ALTER operations are audited. | ## audit_dml_state @@ -100,7 +105,7 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T - **0** indicates that the COPY auditing function is disabled. - **1** indicates that the COPY auditing function is enabled. -**Default value**: **0** +**Default value**: **1** ## audit_set_parameter @@ -115,6 +120,27 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T **Default value**: **1** +## audit_xid_info + +**Parameter description**: Specifies whether to record the transaction ID of the SQL statement in the **detail_info** column of the audit log. + +This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range:** **0** or **1** + +- **0** indicates that the function of recording transaction IDs in audit logs is disabled. +- **1** indicates that the function of recording transaction IDs in audit logs is enabled. + +**Default value**: **0** + +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** If this function is enabled, the **detail_info** information in audit logs starts with **xid**. For example: +> +> ``` +> detail_info: xid=14619 , create table t1(id int); +> ``` +> +> If transaction IDs do not exist, **xid** is recorded as **NA** in audit logs. + ## enableSeparationOfDuty **Parameter description**: Specifies whether the separation of three duties is enabled. diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md index 2efd6fefbac7151b9f469a3dde315e26186611f9..518d13945832219fa864b23ace374bafa6e337c6 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md @@ -131,7 +131,7 @@ The value of **segment_buffers** must be an integer multiple of **BLCKSZ**. C ## bulk_write_ring_size -**Parameter description**: Specifies the size of a ring buffer used for parallel data import. +**Parameter description**: Specifies the size of the ring buffer used by the operation when a large amount of data is written (for example, the copy operation). This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). @@ -198,14 +198,15 @@ This parameter is a USERSET parameter. Set it based on instructions provided in > - For complex serial queries, each query requires five to ten associated operations. Set **work_mem** using the following formula: **work_mem** = 50% of the memory/10. > - For simple serial queries, each query requires two to five associated operations. Set **work_mem** using the following formula: **work_mem** = 50% of the memory/5. > - For concurrent queries, set **work_mem** using the following formula: **work_mem** = **work_mem** for serial queries/Number of concurrent SQL statements. + > - BitmapScan hash tables are also restricted by **work_mem**, but will not be forcibly flushed to disks. In the case of complete lossify, every 1 MB memory occupied by the hash table corresponds to a 16 GB page of BitmapHeapScan (32 GB for Ustore). After the upper limit of **work_mem** is reached, the memory increases linearly with the data access traffic based on this ratio. ## query_mem -**Parameter description**: Specifies the memory used by a query. If the value of **query_mem** is greater than 0, the optimizer adjusts the memory cost estimate to this value when generating an execution plan. +**Parameter description**: Specifies the memory used by a query. This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: 0 or an integer greater than 32 MB. The default unit is KB. If the value is set to a negative value or is less than 32 MB, the default value **0** is used. In this case, the optimizer does not adjust the estimated query memory. +**Value range**: 0 or an integer greater than 32 MB. The default unit is KB. **Default value**: **0** @@ -216,11 +217,11 @@ This parameter is a USERSET parameter. Set it based on instructions provided in ## query_max_mem -**Parameter description**: Specifies the maximum memory that can be used by a query. If the value of **query_max_mem** is greater than 0, an error is reported when the query memory usage exceeds the value. +**Parameter description**: Specifies the maximum memory that can be used by a query. This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: 0 or an integer greater than 32 MB. The default unit is KB. If the value is set to a negative value or a positive integer less than 32 MB, the default value **0** is used. In this case, the optimizer does not limit the query memory. +**Value range**: 0 or an integer greater than 32 MB. The default unit is KB. **Default value**: **0** @@ -242,7 +243,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **Setting suggestions**: > > - The value of this parameter must be greater than that of work_mem so that database dumps can be more quickly cleared or restored. In a database session, only one maintenance operation can be performed at a time. Maintenance is usually performed when there are not many running sessions. - > - When the Automatic Vacuuming process is running, up to autovacuum_max_workers times this memory may be allocated. In this case, set **maintenance_work_mem** to a value greater than or equal to that of work_mem. + > - When the [Automatic Vacuuming](../../../reference-guide/guc-parameters/14-automatic-vacuuming.md) process is running, up to autovacuum_max_workers times this memory may be allocated. In this case, set **maintenance_work_mem** to a value greater than or equal to that of work_mem. > - If a large amount of data is to be clustered, increase the value of this parameter in the session. ## psort_work_mem @@ -286,7 +287,7 @@ This parameter is a SUSET parameter. Set it based on instructions provided in Ta > - The database needs to reserve 640 KB stack depth. Therefore, the ideal setting for this parameter is the actual stack size limit enforced by the OS kernel (as set by **ulimit -s**) minus 640 KB. > - Setting this parameter to a value larger than the actual kernel limit means that a running recursive function may crash an individual backend process. In an OS where MogDB can determine the kernel limit, this parameter cannot be set to an unsafe value. > - Since not all OSs provide this function, you are advised to set a specific value for this parameter. -> - **2 MB** is a small value and will hardly cause system breakdown, +> - The default value is **2 MB**, which is relatively small and does not easily cause system breakdown. ## cstore_buffers @@ -304,7 +305,7 @@ Column-store tables use the shared buffer specified by **cstore_buffers** instea ## bulk_read_ring_size -**Parameter description**: Specifies the ring buffer size used for parallel data export. +**Parameter description**: Specifies the size of the ring buffer used by the operation when a large amount of data is queried (for example, during large table scanning). This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). @@ -324,3 +325,17 @@ This parameter is a USERSET parameter. Set it based on instructions provided in - **off** indicates that the operator memory cannot be released in advance. **Default value**: **on** + +## local_syscache_threshold + +**Parameter description**: Specifies the size of system catalog cache in a session. + +This parameter is a PGC_SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +If **enable_global_plancache** is enabled, **local_syscache_threshold** does not take effect when it is set to a value less than 16 MB to ensure that GPC takes effect. The minimum value is 16 MB. + +If **enable_global_syscache** and **enable_thread_pool** are enabled, this parameter indicates the total cache size of the current thread and sessions bound to the current thread. + +**Value range**: an integer ranging from 1 x 1024 to 512 x 1024. The unit is KB. + +**Default value:** **16 MB** \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md index cce99642743fa64567c4e6b4dd3c3f66c87ff3ae..23e6d4368ebfcf12407f771dccae8654c442eead 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md @@ -17,7 +17,7 @@ This feature allows administrators to reduce the I/O impact of the **VACUUM** an **Background** -During the execution of the ANALYZE | ANALYSE and VACUUM statements, the system maintains an internal counter that keeps track of the estimated cost of the various I/O operations that are performed. When the accumulated cost reaches a limit (specified by **vacuum_cost_limit**), the process performing the operation will sleep for a short period of time (specified by **vacuum_cost_delay**). Then, the counter resets and the operation continues. +During the execution of the [ANALYZE | ANALYSE](../../../reference-guide/sql-syntax/ANALYZE-ANALYSE.md) and [VACUUM](../../../reference-guide/sql-syntax/VACUUM.md) statements, the system maintains an internal counter that keeps track of the estimated cost of the various I/O operations that are performed. When the accumulated cost reaches a limit (specified by **vacuum_cost_limit**), the process performing the operation will sleep for a short period of time (specified by **vacuum_cost_delay**). Then, the counter resets and the operation continues. By default, this feature is disabled. To enable this feature, set **vacuum_cost_delay** to a positive value. @@ -31,7 +31,7 @@ This parameter is usually set to a small value, such as 10 or 20 milliseconds. A This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: an integer ranging from 0 to 100 (unit: ms). A positive number enables cost-based vacuum delay and **0** disables cost-based vacuum delay. +**Value range**: an integer ranging from 0 to 100. A positive number enables cost-based vacuum delay and **0** disables cost-based vacuum delay. **Default value**: **0** diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md index dc6e69d233e23ffa21f0607e6316e596a997db5c..30a5820582565ad9d340f9fe6ab7de7c7e697261 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md @@ -142,3 +142,23 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T - **off**/**false**: The page popularity is not considered. **Default value**: **off** + +## dw_file_num + +**Parameter description**: Specifies the number of doublewrite files to be written in batches. The value is related to **pagewriter_thread_num** and cannot be greater than **pagwriter_thread_num**. If the value is too large, it will be corrected to the value of **pagewriter_thread_num**. + +This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: an integer ranging from 1 to 16 + +**Default value**: **1** + +## dw_file_size + +**Parameter description**: Specifies the size of each doulewrite file. + +This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: an integer, in the range [32,256] + +**Default value**: **256** \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md index ad0d7d9d23153b0640e44a6dc291c2ea3c60accb..656450760443f7d419661badde3917882f836f67 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md @@ -20,11 +20,15 @@ This parameter is a SUSET parameter. Set it based on instructions provided in Ta **Default value**: **off** +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This parameter cannot be enabled on in the current version. Even if it is manually enabled, the system automatically disables it. + ## enable_adio_function **Parameter description**: Specifies whether to enable the ADIO function. -The current version does not support enabling the asynchronous IO function. By default, this function is disabled. Please do not modify it yourself. +This parameter is an INTERNAL parameter, which is fixed. The user cannot modify it but review it only. + +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The current version does not support the asynchronous I/O function. This function is disabled by default. Do not modify the setting. **Value range**: Boolean diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md index cc3349c1d53c5ca0fd501117b3abcaf93d1f019d..1b939dcb03b02363352b46fa285606fb26c7337a 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md @@ -66,23 +66,34 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). +Generally, logs generated by a transaction are synchronized in the following sequence: + +1. The primary node writes the log content to the local memory. +2. The primary node writes the logs in the local memory to the local file system. +3. The primary node flushes logs in the local file system to disks. +4. The primary node sends the log content to the standby node. +5. The standby node receives the log content and saves it to the local memory. +6. The standby node writes logs in the local memory to the local file system. +7. The standby node flushes logs in the local file system to disks. +8. The standby node replays logs to complete the incremental update of data files. + **Value range**: enumerated values -- **on** indicates that synchronization logs of a standby server are flushed to disk. -- **off** indicates asynchronous commit. -- **local** indicates local commit. -- **remote_write** indicates that synchronization logs of a standby server are written to disk. -- **remote_receive** indicates that the standby server receives logs. -- **remote_apply** indicates that the synchronization logs of the standby server are replayed. -- **true** indicates that synchronization logs of a standby server are flushed to disk. -- **false** indicates asynchronous commit. -- **yes** indicates that synchronization logs of a standby server are flushed to disk. -- **no** indicates asynchronous commit. -- **1** indicates that synchronization logs of a standby server are flushed to disk. -- **0** indicates asynchronous commit. -- **2** indicates that the synchronization logs of the standby server are replayed. - -**Default value**: **off** +- **on**: The primary node waits for the standby node to flush logs to disks before committing a transaction. +- **off**: The primary node commits transactions without waiting for the primary node to flush logs to disks. This mode is also called asynchronous commit. +- **local**: The primary node waits for the primary node to flush logs to disks before committing a transaction. This mode is also called local commit. +- **remote_write**: The primary node waits for the standby node to write logs to the file system before committing a transaction. (The logs do not need to be flushed to disks.) +- **remote_receive**: The primary node waits for the standby node to receive logs before committing a transaction. (The logs do not need to be written to the file system.) +- **remote_apply**: The primary node waits for the standby node to complete log replay before committing a transaction. +- **true**: same as **on**. +- **false**: same as **off**. +- **yes**: same as **on**. +- **no**: same as **off**. +- **1**: same as **on**. +- **0**: same as **off**. +- **2**: same as **remote_apply**. + +**Default value**: **on** ## wal_sync_method @@ -96,15 +107,15 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T - **open_datasync** indicates that WAL files are opened with the **O_DSYNC** option. -- **fdatasync** indicates that **fdatasync()** is called at each commit. (SUSE Linux 10 and SUSE Linux 11 are supported.) +- **fdatasync** indicates that **fdatasync()** is called at each commit. - **fsync_writethrough** indicates that **fsync()** is called at each commit to force data in the buffer to be written to the disk. > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **wal_sync_method** can be set to **fsync_writethrough** on a Windows platform, but this setting has the same effect as setting the parameter to **fsync**. -- **fsync** indicates that **fsync()** is called at each commit. (SUSE Linux 10 and SUSE Linux 11 are supported.) +- **fsync** indicates that **fsync()** is called at each commit. (SUSE Linux 10 -- **open_sync** indicates that WAL files are written with **open()** option **O_SYNC**. (SUSE Linux 10 and SUSE Linux 11 are supported.) +- **open_sync** indicates that WAL files are written with **open()** option **O_SYNC**. > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Not all platforms support the preceding parameters. @@ -147,7 +158,7 @@ This parameter is a POSTMASTER parameter. Set it based on instructions provided This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: -1 to 218 +**Value range**: -1 to 2^18. - If this parameter is set to **-1**, the value of **wal_buffers** is automatically changed to 1⁄32 of **shared_buffers**. The minimum value is 8 x **XLOG_BLCKSZ**, and the maximum value is 2048 x **XLOG_BLCKSZ**. That means if the 1⁄32 of **shared_buffers** is smaller than 8 x **XLOG_BLCKSZ** or larger than 2048 x **XLOG_BLCKSZ**, the minimum value or the maximum value is taken. - If this parameter is set to a value other than **-1** and smaller than **4**, the value **4** is used. @@ -254,3 +265,25 @@ When a cluster is faulty, the forcible switchover enables the cluster to recover The value **0** indicates that the function is disabled and the value **1** indicates that the function is enabled. **Default value**: **0** + +## wal_flush_timeout + +**Parameter description**: Specifies the timeout interval for traversing **WalInsertStatusEntryTbl**. It is the maximum wait time for the adaptive Xlog disk flushing I/O to traverse **WalInsertStatusEntryTbl**. + +This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** If the timeout interval is too long, the Xlog flushing frequency may decrease, reducing the Xlog processing performance. + +**Value range**: an integer ranging from 0 to 90000000 (μs) + +**Default value**: **2** + +## wal_flush_delay + +**Parameter description**: Specifies the wait interval when an entry in the **WAL_NOT_COPIED** state is encountered during **WalInsertStatusEntryTbl** traversal. + +This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: an integer ranging from 0 to 90000000 (μs) + +**Default value**: **1** \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md index 239603b7df5b1e82cd687f901bbf385318fdf5ca..2f4d24f16e7e905030f3e6622c6390bf578149b4 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md @@ -15,7 +15,7 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T **Value range**: an integer. The minimum value is **1**. -Increasing the value of this parameter speeds up the export of a large amount of data. Set this parameter based on **[checkpoint_timeout](#checkpoint_timeout)** and **shared_buffers**. This parameter affects the number of WAL segment files that can be reused. Generally, the maximum number of reused files in the **pg_xlog** folder is twice the number of **checkpoint_segments**. The reused files are not deleted and are renamed to the WAL segment files which will be later used. +Increasing the value of this parameter speeds up the export of a large amount of data. Set this parameter based on **[checkpoint_timeout](#checkpoint_timeout)** and [shared_buffers](../../../reference-guide/guc-parameters/4-resource-consumption/1-memory.md#shared_buffers). This parameter affects the number of WAL segment files that can be reused. Generally, the maximum number of reused files in the **pg_xlog** folder is twice the number of **checkpoint_segments**. The reused files are not deleted and are renamed to the WAL segment files which will be later used. **Default value**: **64** @@ -27,7 +27,7 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T **Value range:** an integer ranging from 30 to 3600. The unit is second. -If the value of **[checkpoint_segments](#checkpoint_segments)** is increased, you need to increase the value of this parameter. The increase of these two parameters further requires the increase of **shared_buffers**. Consider all these parameters during setting. +If the value of **[checkpoint_segments](#checkpoint_segments)** is increased, you need to increase the value of this parameter. The increase of these two parameters further requires the increase of [shared_buffers](../../../reference-guide/guc-parameters/4-resource-consumption/1-memory.md#shared_buffers). Consider all these parameters during setting. **Default value**: **15min** @@ -37,7 +37,7 @@ If the value of **[checkpoint_segments](#checkpoint_segments)** is increased, yo This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: a floating point number ranging from 0.0 to 1.0 +**Value range**: a double-precision floating point number ranging from 0.0 to 1.0 **Default value**: **0.5** @@ -104,8 +104,8 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T **Value range**: Boolean -- When set to on, the host will not reclaim logs when any of the standby machines is disconnected. -- When set to off, the host will reclaim the log when any of the standby machines is disconnected. +- If this parameter is set to **on**, the primary node does not recycle logs when any standby node is disconnected. +- If this parameter is set to **off**, the primary node recycles logs when any standby node is disconnected. **Default value**: **on** @@ -121,10 +121,14 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T ## max_size_for_xlog_prune -**Parameter description**: It takes effect when enable_xlog_prune is turned on. If the backup machine is disconnected and the xlog log size is greater than this threshold, the log will be recycled. +**Parameter description**: This parameter takes effect when **enable_xlog_prune** is enabled. The working mechanism is as follows: + +1. If all standby nodes specified by the **replconninfo** series GUC parameters are connected to the primary node, this parameter does not take effect. +2. If any standby node specified by the **replconninfo** series GUC parameters is not connected to the primary node, this parameter takes effect. When the number of historical logs on the primary node is greater than the value of this parameter, the logs are forcibly recycled. Exception: In synchronous commit mode (that is, the value of **synchronous_commit** is not **local** or **off**), if there are connected standby nodes, the primary node retains the logs that meet the minimum log receiving requirements on the majority of standby nodes. In this case, the number of reserved logs may exceed the value of **max_size_for_xlog_prune**. +3. If any standby node is being built, this parameter does not take effect. All logs of the primary node are retained to prevent build failures due to log recycling. This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: integer, 0～2147483647, the unit is KB +**Value range**: an integer ranging from 0 to 2147483647. The unit is KB. -**Default value**: **2147483647,in KB** +**Default value**: **2147483647**. The unit is KB. \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md index dbf25916591a7a61327ce8e07b18c70191e27385..29f8463a70f107c10b8f73d48dd3ae01678fb682 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md @@ -15,7 +15,7 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T **Value range**: an integer ranging from 0 to 3600. The unit is second. -**0** indicates that log flow control is disabled. A value from **1** to **3600** indicates that a standby server can write and replay logs within the period specified by the value, so that the standby server can quickly assume the primary role. If this parameter is set to a small value, the performance of the primary server is affected. If it is set to a large value, the log flow is not effectively controlled. +**0** indicates that log flow control is disabled. A value from **1** to **3600** indicates that a standby server can write and replay logs within the period specified by the value, so that the standby server can quickly assume the primary role. If this parameter is set to a small value, the performance of the primary server is affected. If it is set to a large value, the log flow is not effectively controlled. Because the ultimate RTO has flow control, ultimate RTO prevails when both ultimate RTO and flow control are enabled. During running, flow control is ineffective. **Default value**: **0** @@ -37,7 +37,7 @@ This parameter is a POSTMASTER parameter. Set it based on instructions provided **Value range**: an integer ranging from 1 to 16 -This parameter can be set to a value greater than 1 only when the extreme RTO feature is enabled. In addition, it must be used together with **recovery_redo_workers**. If both **recovery_parse_workers** and **recovery_max_workers** are enabled, the setting of **recovery_parse_workers** prevails and the concurrent replay function is disabled. The extreme RTO feature does not support the hot standby mode or primary/standby/secondary mode. Therefore, **recovery_parse_workers** can be set to a value greater than 1 only when **hot_standby** is set to **off** and **replication_type** to **1**. This feature does not support column-store tables, either. Therefore, disable this feature in a system where column-store tables are used or are to be used. +This parameter can be set to a value greater than 1 only when the extreme RTO feature is enabled. In addition, it must be used together with **recovery_redo_workers**. If both **recovery_parse_workers** and **recovery_max_workers** are enabled, the setting of **recovery_parse_workers** prevails and the concurrent replay function is disabled. The extreme RTO feature does not support the hot standby mode or primary/standby/secondary mode. Therefore, **recovery_parse_workers** can be set to a value greater than 1 only when **hot_standby** is set to **off** and **replication_type** to **1**. This feature does not support column-store tables, either. Therefore, disable this feature in a system where column-store tables are used or are to be used. Because the ultimate RTO has flow control, ultimate RTO prevails when both ultimate RTO and flow control are enabled. During running, flow control is ineffective. **Default value**: **1** @@ -57,9 +57,9 @@ This parameter must be used together with **recovery_parse_workers**, and it tak **Parameter description**: Specifies the actual number of replay threads. This parameter is read-only. -**Value range**: an integer ranging from 1 to 2147483647 +This parameter is a POSTMASTER parameter and is affected by recovery_max_workers and recovery_parse_workers. If any value is greater than 0, recover_parallelism will be recalculated. -This parameter is affected by the parameter: recovery_max_workers and parameter: recovery_parse_workers. When any of the above parameters is greater than 0, the parameter value will be recalculated. +**Value range**: an integer ranging from 1 to 2147483647 **Default value**: **1** @@ -81,8 +81,8 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > -> - This parameter is invalid on the primary node. It must be set on the standby node to be delayed. -> - The delay time is calculated based on the timestamp of transaction submission on the primary server and the current time on the standby server. Therefore, ensure that the clocks of the primary and standby servers are the same. +> - This parameter does not take effect on the primary node. It must be set on the standby node that requires a delay. You are advised to set this parameter on the asynchronous standby node. If the delay is set on the asynchronous standby node, the RTO will be long after the node is promoted to primary. +> - The delay time is calculated based on the transaction commit timestamp on the primary server and the current time on the standby server. Therefore, ensure that the clocks of the primary and standby servers are synchronized. > - If the delay time is too long, the disk where the XLOG file is located on the standby node may be full. Therefore, you need to set the delay time based on the disk size. > - Operations without transactions are not delayed. > - After the primary/standby switchover, if the original primary node needs to be delayed, you need to manually set this parameter. @@ -94,3 +94,15 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T **Value range**: an integer ranging from 0 to INT_MAX. The unit is ms. **Default value**: 0 (no delay added) + +## redo_bind_cpu_attr + +**Parameter description**: Specifies the core binding operation of the replay thread. Only the **sysadmin** user can access this parameter. This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: a string of more than 0 characters. The value is case-insensitive. + +- **'nobind'**: The thread is not bound to a core. +- **'nodebind: 1, 2'**: Use the CPU cores in NUMA groups 1 and 2 to bind threads. +- **'cpubind: 0-30'**: Use the CPU cores 0 to 30 to bind threads. + +**Default value**: **'nobind'** \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md index d9fa45fa30d09170a030c045e29221499cf6c81c..8718b14dab581c08d3062590007a820685868a8b 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md @@ -13,7 +13,11 @@ date: 2021-04-20 This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** When **wal_level** is set to **minimal**, the **archive_mode** parameter is unavailable. +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** +> +> - When **wal_level** is set to **minimal**, the **archive_mode** parameter is unavailable. +> - The archiving function can be enabled on both the synchronous and asynchronous standby nodes. The method of enabling the archiving function is the same as that of enabling the archiving function on a single node. To enable the archiving function, set **archive_mode** to **on** and set **archive_dest** or **archive_command** correctly. +> - If the maximum availability mode is not enabled and the standby node is disconnected from the primary node, the primary node cannot send the archiving location to the standby node due to service congestion. As a result, the archiving fails. **Value range**: Boolean @@ -39,11 +43,11 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T > archive_command = 'cp --remove-destination %p /mnt/server/archivedir/%f' > ``` > -> - **-remove-destination** indicates that files will be overwritten during the archiving. +> - **--remove-destination** indicates that files will be overwritten during the archiving. > > - If there are multiple archive commands, write them to the shell script file and set **archive_command**to the command for executing the script. For example: > -> ``` +> ```sql > -- Assume that multiple commands are as follows: > test ! -f dir/%f && cp %p dir/%f > -- The content of the test.sh script is as follows: diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md index b23fe27d0bce0b1685d0a73604c0427d3419fbac..01aceac19dd0f64c8444f512221f13a8d25622ac 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md @@ -9,13 +9,15 @@ date: 2021-04-20 ## max_wal_senders -**Parameter description**: Specifies the maximum number of simultaneously running WAL sender processes. The value cannot be greater than or equal to that of **max_connections**. +**Parameter description**: Specifies the maximum number of simultaneously running WAL sender processes. The value cannot be greater than or equal to that of [max_connections](../../../reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md#max_connections). This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **wal_level** must be set to **archive** or **hot_standby** to allow the connection from standby servers. +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** [wal_level](../../../reference-guide/guc-parameters/6-write-ahead-log/1-settings.md#wal_level) must be set to **archive** or **hot_standby** to allow the connection from standby servers. -**Value range**: an integer ranging from 0 to 262143 +**Value range**: an integer ranging from 0 to 1024. The recommended value range is 8 to 100. + +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This parameter can be set to 0 only when a single DN is used and there is no primary/standby instance. **Default value:** **16** @@ -56,15 +58,16 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: an integer ranging from 0 to 262143. +**Value range**: an integer ranging from 0 to 1024. The recommended value range is 8 to 100. **Default value**: **8** **Setting suggestions**: -When using logical replication, you are advised to set this parameter to: Number of current physical replication slots + Number of required logical replication slots. +When HA replication, , and logical decoding are used, you are advised to set this parameter to: Number of current physical replication slots + Number of required logical replication slots. If the actual value is smaller than the recommended value, these functions may be unavailable or abnormal. - Physical replication slots provide an automatic method to ensure that Xlogs are not removed from a primary node before they are received by all the standby nodes and secondary nodes. That is, physical replication slots are used to support primary/standby HA. The number of physical replication slots required by a database is equal to the ratio of standby and secondary nodes to the primary node. For example, if an HA database has 1 primary node, 1 standby node, and 1 secondary node, the number of required physical replication slots will be 2. If an HA database has 1 primary node and 3 standby nodes, the number of required physical replication slots will be 3. +- Currently, primary/standby/secondary deployment is not supported by default. - Plan the number of logical replication slots as follows: - A logical replication slot can carry changes of only one database for decoding. If multiple databases are involved, create multiple logical replication slots. - If logical replication is needed by multiple target databases, create multiple logical replication slots in the source database. Each logical replication slot corresponds to one logical replication link. @@ -94,7 +97,7 @@ This parameter is a POSTMASTER parameter. Set it based on instructions provided ## max_cached_tuplebufs -**Parameter description**: Specifies the maximum size (bytes) of the total tuple information buffered in the memory during logic decoding. You are advised to set this parameter to a value greater than or equal to twice of **[max_changes_in_memory](#max_changes_in_memory)**. +**Parameter description**: Specifies the maximum size (bytes) of the total tuple information buffered in the memory during logic decoding. You are advised to set this parameter to a value greater than or equal to twice of [max_changes_in_memory](1-sending-server.md#max_changes_in_memory). This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). @@ -102,263 +105,38 @@ This parameter is a POSTMASTER parameter. Set it based on instructions provided **Default value**: **8192** -## replconninfo1 +## enable_wal_shipping_compression -**Parameter description**: Specifies the information about the first node to be listened to and authenticated by the current server. +**Parameter description**: Specifies whether to enable cross-database instance log compression in streaming DR mode. This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: a string. An empty string indicates that no information about the first node is configured. - -**Default value**: empty - -## replconninfo2 - -**Parameter description**: Specifies the information about the second node to be listened to and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the second node is configured. - -**Default value**: empty - -## replconninfo3 - -**Parameter description**: Specifies the information about the third node to be listened to and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the third node is configured. - -**Default value**: empty - -## replconninfo4 - -**Parameter description**: Specifies the information about the fourth node to be listened to and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the fourth node is configured. - -**Default value**: empty - -## replconninfo5 - -**Parameter description**: Specifies the information about the fifth node to be listened to and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the fifth node is configured. - -**Default value**: empty - -## replconninfo6 - -**Parameter description**: Specifies the information about the sixth node to be listened to and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the sixth node is configured. - -**Default value**: empty - -## replconninfo7 - -**Parameter description**: Specifies the information about the seventh node to be listened to and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the seventh node is configured. - -**Default value**: empty - -## replconninfo8 - -**Parameter description**: Specifies the information about the eighth node to be listened to and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the eighth node is configured. - -**Default value**: an empty string - -## replconninfo9 - -**Parameter description**: Specifies the information about the ninth node to be listened on and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the ninth node is configured. - -**Default value**: empty - -## replconninfo10 - -**Parameter description**: Specifies the information about the tenth node to be listened on and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the tenth node is configured. - -**Default value**: empty - -## replconninfo11 - -**Parameter description**: Specifies the information about the eleventh node to be listened on and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the eleventh node is configured. - -**Default value**: empty - -## replconninfo12 - -**Parameter description**: Specifies the information about the twelfth node to be listened on and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the twelfth node is configured. - -**Default value**: empty - -## replconninfo13 - -**Parameter description**: Specifies the information about the thirteenth node to be listened on and authenticated by the current server. +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** This parameter applies only to a pair of walsender and walreceiver for cross-database instance transmission in streaming DR and is configured on the primary database instance. -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the thirteenth node is configured. - -**Default value**: empty - -## replconninfo14 - -**Parameter description**: Specifies the information about the fourteenth node to be listened on and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the fourteenth node is configured. - -**Default value**: empty - -## replconninfo15 - -**Parameter description**: Specifies the information about the fifteenth node to be listened on and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the fifteenth node is configured. - -**Default value**: empty - -## replconninfo16 - -**Parameter description**: Specifies the information about the sixteenth node to be listened on and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the sixteenth node is configured. - -**Default value**: empty - -## replconninfo17 - -**Parameter description**: Specifies the information about the seventeenth node to be listened on and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the seventeenth node is configured. - -**Default value**: empty - -## replconninfo18 - -**Parameter description**: Specifies the information about the eighteenth node to be listened on and authenticated by the current server. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the eighteenth node is configured. - -**Default value**: empty - -## cross_cluster_replconninfo1 - -**Parameter description**: Specifies the information about the first node to be listened on and authenticated by the current server across clusters. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the first node is configured. - -**Default value**: empty - -## cross_cluster_replconninfo2 - -**Parameter description**: Specifies the information about the second node to be listened on and authenticated by the current server across clusters. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the second node is configured. - -**Default value**: empty - -## cross_cluster_replconninfo3 - -**Parameter description**: Specifies the information about the third node to be listened on and authenticated by the current server across clusters. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the third node is configured. - -**Default value**: empty - -## cross_cluster_replconninfo4 - -**Parameter description**: Specifies the information about the fourth node to be listened on and authenticated by the current server across clusters. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string. An empty string indicates that no information about the fourth node is configured. - -**Default value**: empty - -## cross_cluster_replconninfo5 - -**Parameter description**: Specifies the information about the fifth node to be listened on and authenticated by the current server across clusters. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: a string An empty string indicates that no information about the fifth node is configured. - -**Default value**: empty - -## cross_cluster_replconninfo6 - -**Parameter description**: Specifies the information about the sixth node to be listened on and authenticated by the current server across clusters. - -This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). +**Value range**: Boolean -**Value range**: a string. An empty string indicates that no information about the sixth node is configured. +- **true** indicates that cross-database instance log compression is enabled for streaming DR. +- **false** indicates that cross-database instance log compression is disabled for streaming DR. -**Default value**: empty +**Default value**: **false** -## cross_cluster_replconninfo7 +## replconninfoN -**Parameter description**: Specifies the information about the seventh node to be listened on and authenticated by the current server across clusters. +**Parameter description**: Specifies the information about the *N* node to be listened to and authenticated by the current server (*N* ranges from 1 to 8). This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: a string. An empty string indicates that no information about the seventh node is configured. +**Value range**: a string. An empty string indicates that no information about the *N* node is configured. **Default value**: empty -## cross_cluster_replconninfo8 +## cross_cluster_replconninfoN -**Parameter description**: Specifies the information about the eighth node to be listened on and authenticated by the current server across clusters. +**Parameter description**: Specifies the information about the *N* node to be listened on and authenticated by the current server across clusters (*N* ranges from 1 to 8). This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: a string. An empty string indicates that no information about the eighth node is configured. +**Value range**: a string. An empty string indicates that no information about the *N* node is configured. **Default value**: empty diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md index 055c4eb62707473b6cfc1c7756e419c57ffa419d..60fb55259e840b153c502e556b09d05e6a85b419 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md @@ -16,11 +16,11 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > > - The current synchronous standby server is on the top of the list. If the current synchronous standby server is disconnected, it will be replaced immediately with the next-highest-priority standby server. Name of the next-highest-priority standby server is added to the list. -> - The standby server name can be specified by setting the environment variable **PGAPPNAME**. +> - The standby node name can be specified by setting the environment variable **PGAPPNAME**. **Value range**: a string. If this parameter is set to *****, the name of any standby server that provides synchronous replication is matched. The value can be configured in the following format: -- ANY *num_sync* (*standby_name* [, …]) +- ANY *num_sync* (*standby_name* [, …]) [, ANY *num_sync* (*standby_name* [, …])] - [FIRST] *num_sync* (*standby_name* [, …]) @@ -29,8 +29,9 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** > > - In the preceding command, *num_sync* indicates the number of standby nodes that need to wait for responses from the transaction, *standby_name* indicates the name of the standby node, and FIRST and ANY specify the policies for selecting standby nodes for synchronous replication from the listed servers. - > - **ANY N (dn_instanceId1, dn_instanceId2,…)** indicates that any *N* host names in the brackets are selected as the name list of standby nodes for synchronous replication. For example, ANY 1(dn_instanceId1, dn_instanceId2) indicates that any one of dn_instanceId1 and dn_instanceId2 is used as the standby node for synchronous replication. - > - FIRST N (dn_instanceId1, dn_instanceId2, …) indicates that the first N primary node names in the brackets are selected as the standby node name list for synchronous replication based on the priority. For example, FIRST 1 (dn_instanceId1, dn_instanceId2) indicates that dn_instanceId1 is selected as the standby node for synchronous replication. - The meanings of dn_instanceId1, dn_instanceId2, … are the same as those of FIRST 1 (dn_instanceId1, dn_instanceId2, …). + > - **ANY N (dn_instanceId1, dn_instanceId2,…)** indicates that any *N* host names in the brackets are selected as the name list of standby nodes for synchronous replication. For example, **ANY 1(dn_instanceId1, dn_instanceId2)** indicates that any one of **dn_instanceId1** and **dn_instanceId2** is used as the standby node for synchronous replication. + > - **FIRST N (dn_instanceId1, dn_instanceId2, …)** indicates that the first N primary node names in the brackets are selected as the standby node name list for synchronous replication based on the priority. For example, **FIRST 1 (dn_instanceId1, dn_instanceId2)** indicates that **dn_instanceId1** is selected as the standby node for synchronous replication. + > - The meanings of dn_instanceId1, dn_instanceId2, … are the same as those of FIRST 1 (dn_instanceId1, dn_instanceId2, …). If you use the gs_guc tool to set this parameter, perform the following operations: @@ -59,6 +60,25 @@ This parameter is a POSTMASTER parameter. Set it based on instructions provided **Default value**: **off** +## keep_sync_window + +**Parameter description**: Specifies the delay for entering the maximum availability mode. + +- If **most_available_sync** is set to **on**, when synchronous standby nodes are faulty in primary/standby scenarios and the number of configured synchronous standby nodes is insufficient (for details, see the meaning of **synchonous_standby_name**), setting **keep_sync_window** will retain the maximum protection mode within the time window specified by **keep_sync_window**. That is, committing transactions on the primary node is blocked, delay the primary node to enter the maximum availability mode. +- If synchronous standby nodes recover from faults and the number of synchronous standby nodes meets the configuration requirements, transactions are not blocked. +- You are advised to set **keep_sync_window** to 5s. This prevents the monitoring system from incorrectly reporting network instability. + +This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is second. + +- The value **0** indicates that the **keep_sync_window** is not set, that is, the maximum availability mode is entered directly. +- Other values indicate the size of the timeout window. + +**Default value**: **0** + +> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Setting this parameter may affect the RPO. If the primary node is faulty within the configured timeout window, the data generated from the time when the primary node is blocked to the time when the primary node is faulty may be lost. + ## enable_stream_replication **Parameter description**: Specifies whether data and logs are synchronized between primary and standby servers, and between primary and secondary servers. @@ -69,6 +89,7 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T > > - This parameter is used for performance testing in scenarios where data synchronization to standby server is enabled and where it is disabled. If this parameter is set to **off**, tests on abnormal scenarios, such as switchover and faults, cannot be performed to prevent inconsistency between the primary, standby, and secondary servers. > - This parameter is a restricted parameter, and you are advised not to set it to **off** in normal service scenarios. +> - Currently, primary/standby/secondary deployment is not supported by default. **Value range**: Boolean @@ -85,7 +106,8 @@ This parameter is an INTERNAL parameter. Its default value is **off** and cannot > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > -> This parameter cannot be modified in normal service scenarios. That is, the WAL file and data page mixed replication mode is disabled. +> - This parameter cannot be modified in normal service scenarios. That is, the WAL file and data page mixed replication mode is disabled. +> - Currently, primary/standby/secondary deployment is not supported by default. **Value range**: Boolean @@ -152,7 +174,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in ## enable_incremental_catchup -**Parameter description**: Specifies the data catchup mode between the primary and standby servers. +**Parameter description**: Specifies the data catchup mode between the primary and standby nodes. Currently, primary/standby/secondary deployment is not supported by default. This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). @@ -175,7 +197,8 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** > -> The unit can only be second. +> - The unit can only be second. +> - Currently, primary/standby/secondary deployment is not supported by default. ## catchup2normal_wait_time @@ -207,4 +230,7 @@ This parameter is a POSTMASTER parameter. Set it based on instructions provided > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > -> That the sender initiatively synchronizes the configuration file to the receiver and the receiver requests the sender to synchronize the configuration file is two separate events. Both of them will trigger configuration file synchronization. If you do not want to synchronize the configuration file, you need to configure the receiver as **none_node**. If the sender is a standby server, it can only be configured as **none_node**. If the sender is a primary server and configured as **none_node**, it will not synchronize with all the standby servers. If the sender is a primary server and configured as **only_sync_node**, it will synchronize with the standby servers and not synchronize with the asynchronous standby servers. +> - In a MogDB database instance that contains a primary node, a standby node, and a cascaded standby node, the primary node is a sender relative to the standby node and the standby node is a receiver relative to the primary node, while the standby node is a sender relative to the cascaded standby node and the cascaded standby node is a receiver relative to the standby node. +> - The sender actively synchronizes the configuration file to the receiver, and the receiver requests the sender to synchronize the configuration file, which are two independent events, so that the configuration files are synchronized. If you do not want to synchronize configuration files, set this parameter to **none_node** on the receiver. If the sender is a standby node, set this parameter to **none_node** only. If the sender is a primary node, set this parameter to **none_node** when the primary node does not synchronize with any standby node; or set this parameter to **only_sync_node** when the primary node synchronizes with synchronous standby nodes only and does not synchronize with asynchronous standby nodes. +> - To be specific, the sender sends a configuration file which directly overwrites the corresponding parameter in the configuration file of the receiver. After the policy for synchronizing configuration files is set, even if you modify configuration parameters of the receiver, the modification does not take effect because the sender immediately overwrites these parameters. +> - The following configuration parameters are not synchronized even if the policy for synchronizing configuration files is set: application_name, archive_command, audit_directory, available_zone, comm_control_port, comm_sctp_port, listen_addresses, log_directory, port, replconninfo1, replconninfo2, replconninfo3, replconninfo4, replconninfo5, replconninfo6, replconninfo7, replconninfo8, replconninfo9, replconninfo10, replconninfo11, replconninfo12, replconninfo13, replconninfo14, replconninfo15, replconninfo16, replconninfo17, replconninfo18, ssl, ssl_ca_file, ssl_cert_file, ssl_ciphers, ssl_crl_file, ssl_key_file, ssl_renegotiation_limit, ssl_cert_notify_time, synchronous_standby_names, local_bind_address, perf_directory, query_log_directory, asp_log_directory, streaming_router_port, enable_upsert_to_merge, archive_dest, recovery_min_apply_delay, and sync_config_strategy. diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md index c50975725dc5cce6f93c6fb52862231e5cd76d61..82e005110a913774518c7f65984e6a6e71fdca0b 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md @@ -15,8 +15,12 @@ This parameter is a POSTMASTER parameter. Set it based on instructions provided > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** > -> - If this parameter is set to **on**, **wal_level** must be set to **hot_standby**. Otherwise, the database startup fails. +> - If this parameter is set to **on**, [wal_level](../../../reference-guide/guc-parameters/6-write-ahead-log/1-settings.md#wal_level) must be set to **hot_standby**. Otherwise, the database startup fails. > - In an HA system, **hot_standby** cannot be set to **off**, because this setting can affect other features of the HA system. +> - If the **hot_standby** parameter was disabled and the **wal_level** parameter was set to a value lower than **hot_standby**, perform the following operations to ensure that the logs to be replayed on the standby node can be queried on the standby node before enabling the **hot_standby** parameter again: +> 1. Change the **wal_level** value of the primary and standby nodes to **hot_standby** or higher, and restart the instances for the change to take effect. +> 2. Perform the checkpoint operation on the primary node and query the **pg_stat_get_wal_senders()** function to ensure that the **receiver_replay_location** value of each standby node is the same as the **sender_flush_location** value of the primary node. Ensure that the value adjustment of **wal_level** is synchronized to standby nodes and takes effect, and standby nodes do not need to replay low-level logs. +> 3. Set the **hot_standby** parameter of the primary and standby nodes to **on**, and restart the instances for the setting to take effect. **Value range**: Boolean @@ -114,7 +118,7 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T ## wal_receiver_buffer_size -**Parameter description**: Specifies the memory buffer size for the standby and secondary servers to store the received Xlog files. +**Parameter description**: Specifies the size of the memory buffer that stores the Xlogs received by the standby and secondary nodes. Currently, primary/standby/secondary deployment is not supported by default. This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). @@ -131,3 +135,13 @@ This parameter is a SIGHUP parameter. Set it based on instructions provided in T **Value range**: a string **Default value**: empty + +## max_logical_replication_workers + +**Parameter description**: Specifies the maximum number of apply worker threads on the subscriber side. + +This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: an integer ranging from 0 to 262143 + +**Default value:** **4** \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md index acf6da2d3aa4bac243a05978a0823f43463a4ddc..cc5dc4006749c10a5f8fc0ec689378cb28d875af 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md @@ -111,7 +111,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in - **on** indicates that the query optimizer's use of merge-join plan types is enabled. - **off** indicates that the query optimizer's use of merge-join plan types is disabled. -**Default value**: **off** +**Default value**: **on** ## enable_nestloop @@ -124,7 +124,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in - **on** indicates that the query optimizer's use of nested-loop join plan types is enabled. - **off** indicates that the query optimizer's use of nested-loop join plan types is disabled. -**Default value**: **off** +**Default value**: **on** ## enable_index_nestloop @@ -266,6 +266,38 @@ This parameter is a USERSET parameter. Set it based on instructions provided in **Default value**: **on** +## expected_computing_nodegroup + +**Parameter description**: Specifies a computing Node Group or the way to choose such a group. The Node Group mechanism is now for internal use only. You do not need to set it. + +During join or aggregation operations, a Node Group can be selected in four modes. In each mode, the specified candidate computing Node Groups are listed for the optimizer to select the most appropriate one for the current operator. + +This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: a string + +- **optimal**: The list of candidate computing Node Groups consists of the Node Groups where the operator's operation objects are located and the Node Group that combines all the Node Groups on which the current user has the COMPUTE permission. +- **query**: The list of candidate computing Node Groups consists of the Node Groups where the operator's operation objects are located and the Node Group that combines all the Node Groups where base tables involved in the query are located. +- *Node group name* (when [enable_nodegroup_debug](#enable_nodegroup_debug) is set to **off**): The list of candidate computing Node Groups consists of the Node Group where the operator's operation objects are located and the specified Node Group. +- *Node Group name* (when [enable_nodegroup_debug](#enable_nodegroup_debug) is set to **on**): A specific Node Group is used as the computing Node Group. + +**Default value**: **query** + +## enable_nodegroup_debug + +**Parameter description**: Specifies whether the optimizer assigns computing workloads to a specific Node Group when multiple Node Groups exist in an environment. The Node Group mechanism is now for internal use only. You do not need to set it. + +This parameter takes effect only when [expected_computing_nodegroup](#expected_computing_nodegroup) is set to a specific Node Group. + +This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: Boolean + +- **on** indicates that computing workloads are assigned to the Node Group specified by **expected_computing_nodegroup**. +- **off** indicates no Node Group is specified to compute. + +**Default value**: **off** + ## qrw_inlist2join_optmode **Parameter description**: Specifies whether to enable inlist-to-join (inlist2join) query rewriting. @@ -315,3 +347,27 @@ This parameter is a USERSET parameter. Set it based on instructions provided in - **off** indicates that a check will not be performed. **Default value**: **off** + +## cost_weight_index + +**Parameter description**: Specifies the cost weight of index_scan. + +This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: a floating point number ranging from 1e-10 to 1e+10. + +**Default value**: **1** + +## try_vector_engine_strategy + +**Parameter description**: Specifies the policy for processing row-store tables using the vectorized executor. By setting this parameter, queries containing row-store tables can be converted to vectorized execution plans for calculation, improving the execution performance of complex queries in AP-like scenarios. + +This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Valid value**: enumerated values + +- **off** is the default value, which indicates that this function is disabled. That is, row-store tables will not be converted into vectorized execution plans for execution. +- **force**: Queries are forcibly converted to vectorized execution plans for execution no matter whether the base table to be queried is a row-store table, column-store table, or hybrid row-column store table, unless the query type or expression is not supporte by the vectorized executor. In this case, the performance may deteriorate in different query scenarios. +- **optimal**: On the basis of **force**, the optimizer determines whether to convert a query statement into a vectorized execution plan based on the query complexity to avoid performance deterioration after the conversion. + +**Default value**: **off** \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md index 63444e5b1521e822ecc5bf792c9ae26364e13283..873c03417ac442cc3bd8c32df7e2e0980d692aaa 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md @@ -117,19 +117,6 @@ This parameter is a SUSET parameter. Set it based on instructions provided in Ta **Default value**: **on** -## enable_light_proxy - -**Parameter description**: Specifies whether the optimizer optimizes the execution of simple queries on the primary node of the databases. This parameter does not take effect if the character set of the application side does not match that of the kernel side. You are advised to set the character set to UTF8 when creating a database. - -This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). - -**Value range**: Boolean - -- **on** indicates that the optimizer optimizes the execution of simple queries on the primary node of the databases. -- **off** indicates that the optimizer does not optimize the execution. - -**Default value**: **on** - ## enable_global_plancache **Parameter description**: Specifies whether to share the cache of the PBE query execution plan. Enabling this function can reduce the memory usage of database nodes in high concurrency scenarios. @@ -263,6 +250,9 @@ This parameter is a USERSET parameter. Set it based on instructions provided in - **canonical_pathkey**: after regularization pathkey is generated. (**pathkey**: a set of ordered key values of data.) - **index_cost_with_leaf_pages_only**: Considers index leaf nodes when the index cost is estimated. - **partition_opfusion**: Enables partitioned table optimization. +- **a_style_coerce**: Enables the Decode type conversion rule to be compatible with O. For details, see [Type Resolution for CASE in ORA Compatibility Type](../../../reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md#Type Resolution for CASE in ORA Compatibility Type). +- **partition_fdw_on**: SQL statements can be created for Postgres foreign tables based on partitioned tables. +- **predpush_same_level**: Enables predpush hints to control parameterized paths at the same layer. **Default value**: **none** @@ -315,7 +305,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in > - A larger positive number than the default value increases the time required to do **ANALYZE**, but might improve the quality of the optimizer's estimates. > - Changing settings of this parameter may result in performance deterioration. If query performance deteriorates, you can: > 1. Restore to the default statistics. -> 2. Use hints to force the optimizer to use the optimal query plan. For details, see **Hint-based Tuning**. +> 2. Use hints to force the optimizer to use the optimal query plan. For details, see [Hint-based Tuning](../../../performance-tuning/2-sql/9-hint-based-tuning.md). > - If this parameter is set to a negative value, the number of samples is greater than or equal to 2% of the total data volume, and the number of records in user tables is less than 1.6 million, the time taken by running **ANALYZE** will be longer than when this parameter uses its default value. > - If this parameter is set to a negative value, the auto-analyze function is disabled. @@ -419,7 +409,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Currently, the LLVM optimization only supports the vectorized executor and SQL on Hadoop features. You are advised to set this parameter to **off** in other cases. -**Default value**: **off** +**Default value**: **on** ## codegen_strategy @@ -462,7 +452,9 @@ This parameter is a USERSET parameter. Set it based on instructions provided in ## enable_bloom_filter -**Parameter description**: Specifies whether the BloomFilter optimization can be used. This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). +**Parameter description**: Specifies whether the BloomFilter optimization can be used. + +This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). **Value range**: Boolean @@ -473,7 +465,9 @@ This parameter is a USERSET parameter. Set it based on instructions provided in ## enable_extrapolation_stats -**Parameter description**: Specifies whether the extrapolation logic is used for data of DATE type based on historical statistics. The logic can increase the accuracy of estimation for tables whose statistics are not collected in time, but will possibly provide an overlarge estimation due to incorrect extrapolation. Enable the logic only in scenarios where the data of DATE type is periodically inserted. This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). +**Parameter description**: Specifies whether the extrapolation logic is used for data of DATE type based on historical statistics. The logic can increase the accuracy of estimation for tables whose statistics are not collected in time, but will possibly provide an overlarge estimation due to incorrect extrapolation. Enable the logic only in scenarios where the data of DATE type is periodically inserted. + +This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). **Value range**: Boolean @@ -484,7 +478,9 @@ This parameter is a USERSET parameter. Set it based on instructions provided in ## autoanalyze -**Parameter description**: Specifies whether to automatically collect statistics on tables that have no statistics when a plan is generated. **autoanalyze** cannot be used for foreign or temporary tables. To collect statistics, manually perform the ANALYZE operation. If an exception occurs in the database during the execution of autoanalyze on a table, after the database is recovered, the system may still prompt you to collect the statistics of the table when you run the statement again. In this case, manually perform the ANALYZE operation on the table to synchronize statistics. This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). +**Parameter description**: Specifies whether to automatically collect statistics on tables that have no statistics when a plan is generated. **autoanalyze** cannot be used for foreign or temporary tables. To collect statistics, manually perform the ANALYZE operation. If an exception occurs in the database during the execution of autoanalyze on a table, after the database is recovered, the system may still prompt you to collect the statistics of the table when you run the statement again. In this case, manually perform the ANALYZE operation on the table to synchronize statistics. + +This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). **Value range**: Boolean @@ -520,7 +516,7 @@ This parameter is a USERSET parameter. Set it based on instructions provided in > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** > > - When the hash aggregation operator designed for column-oriented hash tables is used, the memory usage of the query can be reduced. However, in scenarios when enable_codegen is set to **on** and the performance is significantly improved, the performance of the operator may deteriorate. -> - If **enable_sonic_hashagg** is set to **on**, when certain constraints are met, the hash aggregation operator designed for column-oriented hash tables is used and its name is displayed as **Sonic Hash Aggregation** in the output of the Explain Analyze/Performance operation. When the constraints are not met, the operator name is displayed as **Hash Aggregation**. For details, see **Description**. +> - If **enable_sonic_hashagg** is set to **on**, when certain constraints are met, the hash aggregation operator designed for column-oriented hash tables is used and its name is displayed as **Sonic Hash Aggregation** in the output of the Explain Analyze/Performance operation. When the constraints are not met, the operator name is displayed as **Hash Aggregation**. For details, see [Description](../../../performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md#Description). **Default value**: **on** @@ -660,7 +656,11 @@ This parameter is a USERSET parameter. Set it based on instructions provided in This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: Boolean. The value **on** indicates that the function is enabled, and the value **off** indicates that the function is disabled. +**Value range**: Boolean. + +- The value **on** indicates that the function is enabled. + +- The value **off** indicates that the function is disabled. **Default value**: **off** @@ -670,16 +670,32 @@ This parameter is a USERSET parameter. Set it based on instructions provided in This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). -**Value range**: Enumeration type. The value can be **log** or **notice**. **log** indicates that the execution plan is printed in logs. **notice** indicates that the execution plan is printed in notification mode. +**Value range**: Enumeration type. The value can be **log** or **notice**. + +- **log** indicates that the execution plan is printed in logs. + +- **notice** indicates that the execution plan is printed in notification mode. **Default value**: **log** ## query_dop -**Parameter description**: Specifies the user-defined degree of parallelism (DOP). This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). +**Parameter description**: Specifies the user-defined degree of parallelism (DOP). + +This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). **Value range**: an integer ranging from 1 to 64 If the fixed SMP function is enabled, the system uses the fixed DOP. > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** After enabling concurrent queries, ensure you have sufficient CPU, memory, and network to achieve the optimal performance. **Default value**: **1** + +## enable_startwith_debug + +**Parameter description**: Specifies whether to enable the **start with** or **connect by** parameter for debugging. If this parameter is enabled, information about all tail columns related to the **start with** feature is displayed. + +This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](../../../reference-guide/guc-parameters/30-appendix.md). + +**Value range**: Boolean. The value **true** indicates that the function is enabled, and the value **false** indicates that the function is disabled. + +**Default value**: **false** \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md index 708779f133a0a639f3cc50bb6b72967d9c6a4dee..98f7f78f764fb816fcc35b687fe49d08e1ddb99e 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md @@ -26,7 +26,7 @@ date: 2021-04-19 | tup_inserted | bigint | Number of rows inserted by queries in this database | | tup_updated | bigint | Number of rows updated by queries in this database | | tup_deleted | bigint | Number of rows deleted by queries in this database | -| conflicts | bigint | Number of queries canceled due to database recovery conflicts (conflicts occurring only on the standby server). For details, see STAT_DATABASE_CONFLICTS. | +| conflicts | bigint | Number of queries canceled due to database recovery conflicts (conflicts occurring only on the standby server). For details, see [STAT_DATABASE_CONFLICTS](STAT_DATABASE_CONFLICTS.md). | | temp_files | bigint | Number of temporary files created by queries in this database. All temporary files are counted, regardless of why the temporary file was created (for example, sorting or hashing), and regardless of the **log_temp_files** setting. | | temp_bytes | bigint | Total amount of data written to temporary files by queries in this database. All temporary files are counted, regardless of why the temporary file was created, and regardless of the **log_temp_files** setting. | | deadlocks | bigint | Number of deadlocks detected in this database | diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md index 04691c7fabd63dc122c2698927882761990e0333..73a9b77fce1dc3b0c8fc40cbd051daff54241cd4 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md @@ -7,7 +7,7 @@ date: 2021-04-19 # GLOBAL_STAT_SYS_TABLES -**GLOBAL_STAT_SYS_TABLES** displays statistics about the system catalogs of all the namespaces in **pg_catalog** and **information_schema** schemas on each node. +**GLOBAL_STAT_SYS_TABLES** displays statistics about all the system catalogs in the **pg_catalog**, **information_schema**, and **pg_toast** schemas on each node. **Table 1** GLOBAL_STAT_SYS_TABLES columns diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md index 4d969416291887d412eea36e29353f9777b53fd1..1605810f2142d2c5b06f52e29d8cc3da288774f6 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md @@ -25,7 +25,7 @@ date: 2021-04-19 | tup_inserted | bigint | Number of rows inserted by queries in this database | | tup_updated | bigint | Number of rows updated by queries in this database | | tup_deleted | bigint | Number of rows deleted by queries in this database | -| conflicts | bigint | Number of queries canceled due to database recovery conflicts (conflicts occurring only on the standby server). For details, see STAT_DATABASE_CONFLICTS. | +| conflicts | bigint | Number of queries canceled due to database recovery conflicts (conflicts occurring only on the standby server). For details, see [STAT_DATABASE_CONFLICTS](STAT_DATABASE_CONFLICTS.md). | | temp_files | bigint | Number of temporary files created by queries in this database. All temporary files are counted, regardless of why the temporary file was created (for example, sorting or hashing), and regardless of the **log_temp_files** setting. | | temp_bytes | bigint | Total amount of data written to temporary files by queries in this database. All temporary files are counted, regardless of why the temporary file was created, and regardless of the **log_temp_files** setting. | | deadlocks | bigint | Number of deadlocks detected in this database | diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md index aed53176cebd980156594f6d3524a8bf2c327450..c33e4049ecbe116bc3f3a83dbd2ade80f2531861 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md @@ -7,7 +7,7 @@ date: 2021-04-19 # STAT_SYS_TABLES -**STAT_SYS_TABLES** displays statistics about the system catalogs of all the namespaces in **pg_catalog** and **information_schema** schemas. +**STAT_SYS_TABLES** displays statistics about all the system catalogs in the **pg_catalog**, **information_schema**, and **pg_toast** schemas on a single node. **Table 1** STAT_SYS_TABLES columns diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md index 7d21bcff73b3d9c5e935e229e1e4d976489f96e1..69d782f9f9193ad556173a2310806d4bf4261d9a 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md @@ -7,7 +7,7 @@ date: 2021-04-19 # SUMMARY_STAT_SYS_TABLES -**SUMMARY_STAT_SYS_TABLES** displays statistics about the system catalogs of all the namespaces in **pg_catalog** and **information_schema** schemas in MogDB. +**SUMMARY_STAT_SYS_TABLES** displays statistics about all the system catalogs in the **pg_catalog**, **information_schema**, and **pg_toast** schemas in MogDB. **Table 1** SUMMARY_STAT_SYS_TABLES columns diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md index 1fba71d3fb7a7d251a05bc832532bea48d96490d..b248f9210857ca4c26cb85a4abc29bcfb6b0e205 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md @@ -7,4 +7,4 @@ date: 2021-04-19 # GLOBAL_OPERATOR_HISTORY_TABLE -**GLOBAL_OPERATOR_HISTORY_TABLE** displays the records about operators of completed jobs on the primary database node. Data is dumped from the kernel to the system catalog **GS_WLM_OPERATOR_INFO**. **GLOBAL_OPERATOR_HISTORY_TABLE** is a collection view for querying the system catalog **GS_WLM_OPERATOR_INFO** on the primary database node. Columns in this view are the same as those in **[GLOBAL_OPERATOR_HISTORY -> Table 1](GLOBAL_OPERATOR_HISTORY.md)**. +**GLOBAL_OPERATOR_HISTORY_TABLE** displays the records about operators of completed jobs on the primary database node. Data is dumped from the kernel to the system catalog **GS_WLM_OPERATOR_INFO**. **GLOBAL_OPERATOR_HISTORY_TABLE** is a collection view for querying the system catalog **GS_WLM_OPERATOR_INFO** on the primary database node. Columns in this view are the same as those in Table 1 of [GLOBAL_OPERATOR_HISTORY](GLOBAL_OPERATOR_HISTORY.md). \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md index aa8885ba81179bbd6001bcd8673633bd3b8b23f8..f02ff8bb11298bc751e4b7e55ae38379f7924a04 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md @@ -7,4 +7,4 @@ date: 2021-04-19 # OPERATOR_HISTORY -**OPERATOR_HISTORY** displays records of operators in jobs that have been executed by the current user on the current primary database node. Columns in this view are the same as those in **[Appendices-Table 6](../../../../reference-guide/schema/DBE_PERF/appendices/table-6.md)**. +**OPERATOR_HISTORY** displays records of operators in jobs that have been executed by the current user on the current primary database node. Columns in this view are the same as those in Table 1 of [GS_WLM_OPERATOR_INFO](../../../../reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md). \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md index ee1839ccf2545aa6c7c94ec41500c85c99ba8bd1..9474ab38cf2508e0c7c5e9c6702a223e97897b34 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md @@ -7,13 +7,13 @@ date: 2021-04-19 # GLOBAL_DOUBLE_WRITE_STATUS -**GLOBAL_DOUBLE_WRITE_STATUS** displays doublewrite file status of all instances in MogDB. +**GLOBAL_DOUBLE_WRITE_STATUS** displays doublewrite file status of all instances in MogDB. It consists of the **local_double_write_stat** view of each node. Columns in the view on each node are the same. **Table 1** GLOBAL_DOUBLE_WRITE_STATUS columns | Name | Type | Description | | :-------------------- | :----- | :----------------------------------------------------------- | -| node_name | text | node name | +| node_name | text | Node name | | curr_dwn | bigint | Sequence number of the doublewrite file | | curr_start_page | bigint | Start page for restoring the doublewrite file | | file_trunc_num | bigint | Number of times that the doublewrite file is reused | @@ -24,3 +24,4 @@ date: 2021-04-19 | total_pages | bigint | Total number of pages that are flushed to the doublewrite file area | | low_threshold_pages | bigint | Number of pages that are flushed with low efficiency | | high_threshold_pages | bigint | Number of pages that are flushed with high efficiency | +| file_id | bigint | ID of the current doublewrite file | diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md index bb91fbabf2b071ee2d239e63e903b1168d965107..d998d669cb867ce226f33bcbe089fd85005f010a 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md @@ -7,7 +7,7 @@ date: 2021-04-19 # WAIT_EVENTS -**WAIT_EVENTS** displays statistics about wait events on the current node. For details about events, see **[Appendices-Table 1](../../../../reference-guide/schema/DBE_PERF/appendices/table-1.md)**, **[Appendices-Table 2](../../../../reference-guide/schema/DBE_PERF/appendices/table-2.md)**, **[Appendices-Table 3](../../../../reference-guide/schema/DBE_PERF/appendices/table-3.md)**, and **[Appendices-Table 4](../../../../reference-guide/schema/DBE_PERF/appendices/table-4.md)**. For details about the extent to which each transaction lock affects the services, see [LOCK](../../../../reference-guide/sql-syntax/110-LOCK.md). +**WAIT_EVENTS** displays statistics about wait events on the current node. For details about events, see Table 2, Table 3, and Table 4 in [PG_THREAD_WAIT_STATUS](../../../../reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md). For details about the extent to which each transaction lock affects the services, see [LOCK](../../../../reference-guide/sql-syntax/110-LOCK.md). **Table 1** WAIT_EVENTS columns diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md index c636fb8f856b7a79cde1c94bd374980e4aa2c7c2..0c3496d51d1f3d0e2fd52af640d154dbd343065d 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md @@ -17,3 +17,4 @@ During debugging on the debug end, call **info_breakpoints** to view the current | funcoid | OUT oid | Function ID | | lineno | OUT integer | Line number | | query | OUT text | Breakpoint content | +| enable | OUT boolean | Valid or not | diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md index 10d57aa3308ee123d030ee92883d4b2c58bc7ade..90cd286590100004c414568f3acb4f1e9e2c6c55 100644 --- a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md @@ -24,19 +24,19 @@ Two clients are required to connect to the database. One client is responsible f Use PG_PROC to find the OID of the stored procedure to be debugged and execute **DBE_PLDEBUGGER.turn_on(oid)**. In this case, the client functions as the server. ```sql - mogdb=# CREATE OR REPLACE PROCEDURE test_debug ( IN x INT) + MogDB=# CREATE OR REPLACE PROCEDURE test_debug ( IN x INT) AS BEGIN INSERT INTO t1 (a) VALUES (x); END; / CREATE PROCEDURE - mogdb=# SELECT OID FROM PG_PROC WHERE PRONAME='test_debug'; + MogDB=# SELECT OID FROM PG_PROC WHERE PRONAME='test_debug'; oid ------- 16389 (1 row) - mogdb=# SELECT * FROM DBE_PLDEBUGGER.turn_on(16389); + MogDB=# SELECT * FROM DBE_PLDEBUGGER.turn_on(16389); nodename | port ----------+------ datanode | 0 @@ -48,13 +48,13 @@ Two clients are required to connect to the database. One client is responsible f When the server executes the stored procedure, the server hangs before the first SQL statement in the stored procedure and waits for the debugging message sent by the debug end. Debugging is supported only by directly executing a stored procedure and cannot be achieved by invoking an executed stored procedure through a trigger. ```sql - mogdb=# call test_debug(1); + MogDB=# call test_debug(1); ``` Start another client as the debug end and invoke **DBE_PLDEBUGGER.attach** to attach with the stored procedure for debugging based on the data returned by **turn_on**. ```sql - mogdb=# SELECT * FROM DBE_PLDEBUGGER.attach('datanode',0); + MogDB=# SELECT * FROM DBE_PLDEBUGGER.attach('datanode',0); funcoid | funcname | lineno | query ---------+------------+--------+---------------------------------- 16389 | test_debug | 3 | INSERT INTO t1 (a) VALUES (x); @@ -64,7 +64,7 @@ Two clients are required to connect to the database. One client is responsible f Execute the next statement on the client where the attach operation is performed. ```sql - mogdb=# SELECT * FROM DBE_PLDEBUGGER.next(); + MogDB=# SELECT * FROM DBE_PLDEBUGGER.next(); funcoid | funcname | lineno | query ---------+------------+--------+---------------------- 16389 | test_debug | 0 | [EXECUTION FINISHED] @@ -74,7 +74,7 @@ Two clients are required to connect to the database. One client is responsible f Output all the current variables on the client where the attach command is executed. ```sql - mogdb=# SELECT * FROM DBE_PLDEBUGGER.info_locals(); + MogDB=# SELECT * FROM DBE_PLDEBUGGER.info_locals(); varname | vartype | value | package_name ---------+---------+-------+-------------- $1 | int4 | 1 | @@ -84,7 +84,7 @@ Two clients are required to connect to the database. One client is responsible f Directly execute the stored procedure that is being debugged. ```sql - mogdb=# SELECT * FROM DBE_PLDEBUGGER.continue(); + MogDB=# SELECT * FROM DBE_PLDEBUGGER.continue(); funcoid | funcname | lineno | query ---------+------------+--------+---------------------- 16389 | test_debug | 0 | [EXECUTION FINISHED] @@ -94,7 +94,7 @@ Two clients are required to connect to the database. One client is responsible f Exit the stored procedure that is being debugged and do not execute statements that have not been executed before. ```sql - mogdb=# SELECT * FROM DBE_PLDEBUGGER.abort(); + MogDB=# SELECT * FROM DBE_PLDEBUGGER.abort(); abort ------- t diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEVELOPER/DBE_PLDEVELOPER.gs_errors.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEVELOPER/DBE_PLDEVELOPER.gs_errors.md new file mode 100644 index 0000000000000000000000000000000000000000..85e50e19ea325978987b6ffa0db622a5d8d7cacc --- /dev/null +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEVELOPER/DBE_PLDEVELOPER.gs_errors.md @@ -0,0 +1,24 @@ +--- +title: DBE_PLDEVELOPER.gs_errors +summary: DBE_PLDEVELOPER.gs_errors +author: Guo Huan +date: 2022-05-31 +--- + +# DBE_PLDEVELOPER.gs_errors + +Records errors that occur during PLPGSQL object (stored procedure, function, package, and package body) compilation. For details, see the following column description. + +After the **plsql_show_all_error** parameter is enabled, if an error occurs during compilation, the error is skipped and the compilation continues, and the error information is recorded in **gs_errors**. If the **plsql_show_all_error** parameter is disabled, related information is not inserted into this table. + +**Table 1** DBE_PLDEVELOPER.gs_errors columns + +| **Name** | **Type** | **Description** | +| -------- | -------- | ------------------------------------------------------------ | +| id | oid | Object ID. | +| owner | bigint | ID of the user who creates the object. | +| nspid | oid | Schema ID of an object. | +| name | name | Object name. | +| type | text | Object type (**procedure**/**function**/**package**/**package body**). | +| line | integer | Line number. | +| src | text | Original statement for creating an object. | \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEVELOPER/DBE_PLDEVELOPER.gs_source.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEVELOPER/DBE_PLDEVELOPER.gs_source.md new file mode 100644 index 0000000000000000000000000000000000000000..7225caeb15d90a5c56ead5084ec83a78b13aa1d3 --- /dev/null +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEVELOPER/DBE_PLDEVELOPER.gs_source.md @@ -0,0 +1,24 @@ +--- +title: DBE_PLDEVELOPER.gs_source +summary: DBE_PLDEVELOPER.gs_source +author: Guo Huan +date: 2022-05-31 +--- + +# DBE_PLDEVELOPER.gs_source + +Records PLPGSQL object (stored procedure, function, package, and package body) compilation information. For details, see the following column description. + +When the **plsql_show_all_error** parameter is enabled, information about PL/PGSQL object compilation success or failure is recorded in this table. When the **plsql_show_all_error** parameter is disabled, only information about correct compilation is inserted into this table. + +**Table 1** DBE_PLDEVELOPER.gs_source columns + +| **Name** | **Type** | **Description** | +| -------- | -------- | ------------------------------------------------------------ | +| id | oid | Object ID. | +| owner | bigint | ID of the user who creates the object. | +| nspid | oid | Schema ID of an object. | +| name | name | Object name. | +| type | text | Object type (**procedure**/**function**/**package**/**package body**). | +| status | boolean | Determines whether the creation is successful. | +| src | text | Original statement for creating an object. | \ No newline at end of file diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEVELOPER/overview-of-DBE_PLDEVELOPER.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEVELOPER/overview-of-DBE_PLDEVELOPER.md new file mode 100644 index 0000000000000000000000000000000000000000..e7fb92e2637991f3edfadddbbbc03aa037794032 --- /dev/null +++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEVELOPER/overview-of-DBE_PLDEVELOPER.md @@ -0,0 +1,10 @@ +--- +title: DBE_PLDEVELOPER +summary: DBE_PLDEVELOPER +author: Guo Huan +date: 2022-05-31 +--- + +# DBE_PLDEVELOPER + +The system table in DBE_PLDEVELOPER records information required for compiling PLPGSQL packages, functions, and stored procedures. diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md b/product/zh/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md index 3f0dd113871b16f227b1402222b544634d63f4d1..78c6c0c8ac7b705c1e675f8913d3a6130659e583 100644 --- a/product/zh/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md +++ b/product/zh/docs-mogdb/v3.0/installation-guide/installation-preparation/environment-requirement.md @@ -71,5 +71,3 @@ date: 2021-04-2 | libnsl（openEuler+x86环境中） | 建议版本：2.28-36 | | openSSH | 建议版本 ：8.4p1 | | expect | 建议版本 ：5.45.4 | - -注：实际测试4G内存也能安装（需要修改配置文件内存参数），4G以上内存不需要修改。 \ No newline at end of file