v1.1

Developer Options

allow_system_table_mods

Parameter description: Specifies whether the structures of system tables can be modified.

This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

It is not recommended to modify the default value of this parameter. If it is set to on, the system tables may be damaged and the database may not start.

Value range: Boolean

on indicates that the structures of system tables can be modified.
off indicates that the structures of system tables cannot be modified.

Default value: off

debug_assertions

Parameter description: Specifies whether to enable various assertion checks. This parameter assists in debugging. If you are experiencing strange problems or crashes, set this parameter to on to identify programming defects. To use this parameter, the macro USE_ASSERT_CHECKING must be defined (through the configure option -enable-cassert) during the MogDB compilation.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that various assertion checks are enabled.
off indicates that various assertion checks are disabled.

NOTE: This parameter is set to on by default if MogDB is compiled with various assertion checks enabled.

Default value: off

ignore_checksum_failure

Parameter description: Specifies whether to ignore check failures (but still generates an alarm) and continues reading data. Continuing reading data may result in breakdown, damaged data being transferred or hidden, failure of data recovery from remote nodes, or other serious problems. You are not advised to modify the settings.

This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that data check errors are ignored.
off indicates that data check errors are reported.

Default value: off

enable_force_vector_engine

Parameter description: Specifies whether to forcibly generate vectorized execution plans for a vectorized execution operator if the operator's child node is a non-vectorized operator. When this parameter is set to on, vectorized execution plans are forcibly generated.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on means that vectorized operators are forced to generate vectorization.
off means that the vector operator optimizer decides whether to vectorize.

Default value: off

explain_dna_file

Parameter description: Sets explain_perf_mode to run to export object files in CSV format.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

NOTICE: The value of this parameter must be an absolute path plus a file name with the extension .csv.

Value range: a string

Default value: empty

explain_perf_mode

Parameter description: Specifies the display format of the explain command.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: normal, pretty, summary, and run

normal indicates that the default printing format is used.
pretty indicates a new format improved by using MogDB. A new format contains a plan node ID, directly and effectively analyzing performance.
summary indicates that the analysis result on this information is printed in addition to the printed information in the format specified by pretty.
run indicates that in addition to the printed information specified by summary, the database exports the information as a CSV file.

Default value: normal

ignore_system_indexes

Parameter description: specifies whether to ignore system indexes when reading system tables (but still update the indexes when modifying the tables).

This parameter is a BACKEND parameter. Set it based on instructions provided in Table 1 GUC parameters.

NOTICE: This parameter is useful for recovering data from tables whose system indexes are damaged.

Value range: Boolean

on indicates that system indexes are ignored.
off indicates that system indexes are not ignored.

Default value: off

post_auth_delay

Parameter description: Specifies the delay in the connection to the server after a successful authentication. Developers can attach a debugger to the server startup process.

This parameter is a BACKEND parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: an integer ranging from 0 to 2147. The unit is s.

Default value: 0

pre_auth_delay

Parameter description: Specifies the period of delaying authentication after the connection to the server is started. Developers can attach a debugger to the authentication procedure.

This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: an integer ranging from 0 to 60. The unit is s.

Default value: 0

trace_notify

Parameter description: Specifies whether to generate a large amount of debugging output for the LISTEN and NOTIFY commands. The level of client_min_messages or log_min_messages must be DEBUG1 or lower to send such output to the client or server logs, respectively.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the function is enabled.
off indicates that the function is disabled.

Default value: off

trace_recovery_messages

Parameter description: Specifies whether to enable logging of recovery-related debugging output. This parameter allows users to overwrite the normal setting of log_min_messages, but only for specific messages. This is intended for the use in debugging the standby server.

This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: enumerated values. Valid values include debug5, debug4, debug3, debug2, debug1, and log. For details about the parameter values, see log_min_messages.

Default value: log

NOTE:

log indicates that recovery-related debugging information will not be logged.

Except the default value log, each of the other values indicates that recovery-related debugging information at the specified level will also be logged. Common settings of log_min_messages will unconditionally record information into server logs.

trace_sort

Parameter description: Specifies whether to print information about resource usage during sorting operations. This parameter is available only when the macro TRACE_SORT is defined during the MogDB compilation. However, TRACE_SORT is currently defined by default.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the function is enabled.
off indicates that the function is disabled.

Default value: off

zero_damaged_pages

Parameter description: Specifies whether to detect a damaged page header that causes MogDB to report an error, aborting the current transaction.

This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

Setting this parameter to on causes the system to report a warning, zero out the damaged page, and continue processing. This behavior will destroy data, including all the rows on the damaged page. However, it allows you to bypass the error and retrieve rows from any undamaged pages that may be present in the table. Therefore, it is useful for restoring data if corruption has occurred due to a hardware or software error. In most cases, you are advised not to set this parameter to on unless you do not want to restore data from the damaged pages of a table.

Default value: off

string_hash_compatible

Parameter description: specifies whether to use the same method to calculate char-type hash values and varchar- or text-type hash values. Based on the setting of this parameter, you can determine whether a redistribution is required when a distribution column is converted from a char-type data distribution into a varchar- or text-type data distribution.

This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the same calculation method is used and a redistribution is not required.
off indicates that different calculation methods are used and a redistribution is required.

NOTE: Calculation methods differ in the length of input strings used for calculating hash values. (For a char-type hash value, spaces following a string are not counted as the length. For a text- or varchar-type hash value, the spaces are counted.) The hash value affects the calculation result of queries. To avoid query errors, do not modify this parameter during database running once it is set.

Default value: off

cost_param

Parameter description: Controls use of different estimation methods in specific customer scenarios, allowing estimated values approximating to onsite values. This parameter can control various methods simultaneously by performing AND (&) on the bit of each method. A method is selected if the result value is not 0.

When cost_param & 1 is set to a value other than 0, an improved mechanism is used for estimating the selection rate of non-equi-joins. This method is more accurate for estimating the selection rate of joins between two identical tables. At present, cost_param & 1=0 is not used. That is, a better formula is selected for calculation.

When cost_param & 2 is set to a value other than 0, the selection rate is estimated based on multiple filter criteria. The lowest selection rate among all filter criteria, but not the product of the selection rates for two tables under a specific filter criterion, is used as the total selection rate. This method is more accurate when a close correlation exists between the columns to be filtered.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: an integer ranging from 0 to INT_MAX

Default value: 0

convert_string_to_digit

Parameter description: Specifies the implicit conversion priority, which determines whether to preferentially convert strings into numbers.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that strings are preferentially converted into numbers.
off indicates that strings are not preferentially converted into numbers.

Default value: on

NOTICE: Modify this parameter only when absolutely necessary because the modification will change the rule for converting internal data types and may cause unexpected results.

nls_timestamp_format

Parameter description: Specifies the default timestamp format.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string

Default value: DD-Mon-YYYY HH:MI:SS.FF AM

remotetype

Parameter description: Specifies the remote connection type.

This parameter is a BACKEND parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: enumerated values. Valid values are application, datanode, and internaltool.

Default value: application

enable_partitionwise

Parameter description: Specifies whether to select an intelligent algorithm for joining partition tables.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that an intelligent algorithm is selected.
off indicates that an intelligent algorithm is not selected.

Default value: off

max_function_args

Parameter description: Specifies the maximum number of parameters allowed for a function.

This parameter is an INTERNAL parameter. The value of this parameter cannot be modified.

Value range: an integer.

Default value: 666

max_user_defined_exception

Parameter description: Specifies the maximum number of exceptions. The default value cannot be changed.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: an integer. Currently, only the fixed value 1000 is supported.

Default value: 1000

enable_debug_vacuum

Parameter description: Specifies whether to allow output of some VACUUM-related logs for problem locating. This parameter is used only by developers. Common users are advised not to use it.

This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on/true indicates that output of VACUUM-related logs is allowed.
off/false indicates that output of VACUUM-related logs is disallowed.

Default value: off

enable_global_stats

Parameter description: Specifies the current statistics collection mode, which can be global statistics collection or single-node statistics collection. By default, the global statistics collection mode is used. If this parameter is set to off, the statistics of the first node in MogDB are collected by default. In this case, the quality of the generated query plan may be affected. However, the information collection performance is optimal. Therefore, exercise caution when disabling this parameter.

This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on or true indicates the global statistics mode.
off or false indicates the database node statistics.

Default value: on

enable_fast_numeric

Parameter description: Specifies whether to enable optimization for numeric data calculation. Calculation of numeric data is time-consuming. Numeric data is converted into int64- or int128-type data to improve numeric data calculation performance.

This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on or true indicates that optimization for numeric data calculation is enabled.
off or false indicates that optimization for numeric data calculation is disabled.

Default value: on

rewrite_rule

Parameter description: Specifies the rewriting rule for enabled optional queries. Some query rewrite rules are optional. Enabling them cannot always improve the query efficiency. In a specific customer scenario, you can set the query rewriting rules through the GUC parameter to achieve optimal query efficiency.

This parameter can control the combination of query rewriting rules, for example, there are over one override rules: rule1, rule2, rule3, and rule4. To set the parameters, you can perform the following operations:

set rewrite_rule=rule1;          -- Enable query rewriting rule rule1
set rewrite_rule=rule2, rule3;     -- Enable the query rewriting rules rule2 and rule3
set rewrite_rule=none;         -- Disable all optional query rewriting rules

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string

none: Does not use any optional query rewriting rules
lazyagg: Uses the Lazy Agg query rewriting rules for eliminating aggregation operations in subqueries.

Default value: magicset

enable_compress_spill

Parameter description: Specifies whether to enable the compression function of writing data to disk.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on or true indicates that optimization for writing data to disk is enabled.
off or false indicates that optimization for writing data to disk is disabled.

Default value: on

analysis_options

Parameter description: Specifies whether to enable function options in the corresponding options to use the corresponding location functions, including data verification and performance statistics. For details, see the options in the value range.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string

LLVM_COMPILE indicates that the codegen compilation time of each thread is displayed on the explain performance page.
HASH_CONFLICT indicates that the log file in the pg_log directory of the database node process displays the hash table statistics, including the hash table size, hash chain length, and hash conflict information.
STREAM_DATA_CHECK indicates that a CRC check is performed on data before and after network data transmission.

Default value: ALL,on(),off(LLVM_COMPILE,HASH_CONFLICT,STREAM_DATA_CHECK), which indicates that no location function is enabled.

NOTICE: Use on() oroff() to enable or disable the functions. The function options that are not displayed retain the original values. Format for reference: 'on(option1, option2, …)' 'off(ALL)'

resource_track_log

Parameter description: Specifies the log level of self-diagnosis. Currently, this parameter takes effect only in multi-column statistics.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string

summary: Brief diagnosis information is displayed.
detail: Detailed diagnosis information is displayed.

Currently, the two parameter values differ only when there is an alarm about multi-column statistics not collected. If the parameter is set to summary, such an alarm will not be displayed. If it is set to detail, such an alarm will be displayed.

Default value: summary

udf_memory_limit

Parameter description: Controls the maximum physical memory that can be used when each database node executes UDFs.

This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: an integer. The value range is from 200 x 1024 to max_process_memory and the unit is KB.

Default value: 200MB

FencedUDFMemoryLimit

Parameter description: Specifies the virtual memory used by each fenced udf worker process.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Suggestion: You are not advised to set this parameter. You can set udf_memory_limit instead.

Value range: an integer ranging from 0 KB to 2147483647 KB. The unit can also be MB or GB. 0 indicates that the memory is not limited.

Default value: 0

UDFWorkerMemHardLimit

Parameter description: Specifies the maximum value of fencedUDFMemoryLimit.

This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

Suggestion: You are not advised to set this parameter. You can set udf_memory_limit instead.

Value range: an integer ranging from 0KB to 2147483647KB. The unit can also be MB or GB.

Default value: 1GB

pljava_vmoptions

Parameter description: Specifies the startup parameters for JVMs used by the PL/Java function.

This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string, supporting:

JDK8 JVM startup parameters. For details, see JDK official descriptions.
JDK8 JVM system attributes (starting with -D, for example, -Djava.ext.dirs). For details, see JDK official descriptions.
User-defined parameters (starting with -D, for example, -Duser.defined.option).

NOTICE: If pljava_vmoptions is set to a value beyond the value range, an error will be reported when PL/Java functions are used. For details, see PL/pgSQL Functions.

Default value: empty

enable_pbe_optimization

Parameter description: Specifies whether the optimizer optimizes the query plan for statements executed in Parse Bind Execute (PBE) mode.

This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the optimizer optimizes the query plan.
off indicates that the optimizer does not optimize the execution.

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.

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.

This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the execution plan of the PBE query is shared in the cache.
off indicates that the execution plan of the PBE query is not shared in the cache.

Default value: off

checkpoint_flush_after

Parameter description: Specifies the number of consecutive disk pages that the checkpointer writer thread writes before asynchronous flush. In MogDB, the disk page size is 8 KB.

This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: an integer ranging from 0 to 256. 0 indicates that the asynchronous flush function is disabled. For example, if the value is 32, the checkpointer thread continuously writes 32 disk pages (that is, 32 x 8 = 256 KB) before asynchronous flush.

Default value: 32

bgwriter_flush_after

Parameter description: Specifies the number of consecutive disk pages that the background writer thread writes before asynchronous flush. In MogDB, the disk page size is 8 KB.

This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: an integer ranging from 0 to 256. 0 indicates that the asynchronous flush function is disabled. The size of a single page is 8 KB. For example, if the value is 64, the background writer thread continuously writes 64 disk pages (that is, 64 x 8 = 512 KB) before asynchronous flush.

Default value: 512KB (64 pages)

backend_flush_after

Parameter description: Specifies the number of consecutive disk pages that the backend thread writes before asynchronous flush. In MogDB, the disk page size is 8 KB.

This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: an integer ranging from 0 to 256. 0 indicates that the asynchronous flush function is disabled. The size of a single page is 8 KB. For example, if the value is 64, the backend thread continuously writes 64 disk pages (that is, 64 x 8 = 512 KB) before asynchronous flush.

Default value: 0

enable_parallel_ddl

Parameter description: Specifies whether multiple database nodes can concurrently perform DDL operations on the same database object.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on: DDL operations can be concurrently performed without distributed deadlocks.
off: Distributed deadlocks may occur when DDL operations are concurrently performed.

Default value: on

show_acce_estimate_detail

Parameter description: The evaluation information is generally used by O&M personnel during maintenance, and it may affect the output display of the EXPLAIN statement. Therefore, this parameter is disabled by default. The evaluation information is displayed only if the verbose option of the EXPLAIN statement is enabled.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the evaluation information is displayed in the output of the EXPLAIN statement.
off indicates that the evaluation information is not displayed in the output of the EXPLAIN statement.

Default value: off

enable_prevent_job_task_startup

Parameter description: Specifies whether to start the job thread.

This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the job thread is not started.
off indicates that the job thread is started.

Default value: off

enable_early_free

Parameter description: Specifies whether the operator memory can be released in advance.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the operator memory can be released in advance.
off indicates that the operator memory cannot be released in advance.

Default value: on

support_batch_bind

Parameter description: Specifies whether to batch bind and execute PBE statements through interfaces such as JDBC, ODBC, and Libpq.

This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that batch binding and execution are used.
off indicates that batch binding and execution are not used.

Default value: on

check_implicit_conversions

Parameter description: Specifies whether to check candidate index paths generated for index columns that have implicit type conversions in a query.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that a check will be performed for candidate index paths generated for index columns that have implicit type conversion in a query.
off indicates that a check will not be performed.

Default value: off

enable_thread_pool

Parameter description: Specifies whether to enable the thread pool function. This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the thread pool function is enabled.
off indicates that the thread pool function is disabled.

Default value: off

thread_pool_attr

Parameter description: Specifies the detailed attributes of the thread pool function. This parameter is valid only when enable_thread_pool is set to on. This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string, consisting of one or more characters.

This parameter consists of three parts: thread_num, group_num, and cpubind_info. The meanings of the three parts are as follows:

thread_num indicates the total number of threads in the thread pool. The value ranges from 0 to 4096. The value 0 indicates that the database automatically configures the number of threads in the thread pool based on the number of CPU cores. If the value is greater than 0, the number of threads in the thread pool is the same as the value of thread_num.
group_num indicates the number of thread groups in the thread pool. The value ranges from 0 to 64. The value 0 indicates that the database automatically configures the number of thread groups in the thread pool based on the number of NUMA groups. If the value is greater than 0, the number of thread groups in the thread pool is the same as the value of group_num.
cpubind_info indicates whether the thread pool is bound to a core. The available configuration modes are as follows: 1. '(nobind)': The thread is not bound to a core. 2. '(allbind)': Use all CPU cores that can be queried in the current system to bind threads. 3. '(nodebind: 1, 2)': Use the CPU cores in NUMA groups 1 and 2 to bind threads. 4. '(cpubind: 0-30)': Use the CPU cores 0 to 30 to bind threads. This parameter is case-insensitive.

Default value: '16, 2, (nobind)'

numa_distribute_mode

Parameter description: Specifies the distribution of some shared data and threads among NUMA nodes. This parameter is used to optimize the performance of large-scale ARM servers with multiple NUMA nodes. Generally, you do not need to set this parameter.

This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string. The valid values are none and all.

none indicates that this function is disabled.
all indicates that some shared data and threads are distributed to different NUMA nodes to reduce the number of remote access times and improve performance. Currently, this function applies only to ARM servers with multiple NUMA nodes. All NUMA nodes must be available for database processes. You cannot select only some NUMA nodes.

Default value: none

log_pagewriter

Parameter description: Specifies whether to display the page refresh information of a thread and details about an incremental check point after the incremental check point is enabled. You are not advised to set this parameter to true because a large amount of information will be generated.

This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

Default value: off

enable_opfusion

Parameter description: Specifies whether to optimize simple queries.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

The constraints for simple query are as follows:

Only indexscan and indexonlyscan are supported, and all WHERE statements are filtered on the index.
The addition, deletion, modification, query operations can be performed only on a single table. join and using are not supported.
Only row-store tables are supported. Partition tables are not supported. Tables do not support triggers included.
Active SQL, QPS and other information statistics features are not supported.
Tables that are expanding or shrinking are not supported.
Querying or modifying system columns is not supported.
Only simple SELECT statements are supported. For example,
```
SELECT c3 FROM t1 WHERE c1 = ? and c2 =10;
```
You can query only the columns of the target table. C1 and C2 are indexed columns, followed by either constants or parameters. You can use FOR UPDATE.
Only simple INSERT statements are supported. For example,
```
INSERT INTO t1 VALUES (?,10,?);
```
Only one VALUES is supported, and the types in VALUES can be constants and parameters. Returning is not supported.
Only simple DELETE statements are supported. For example,
```
DELETE FROM t1 WHERE c1 = ? and c2 = 10;
```
C1 and C2 are indexed columns, followed by either constants or parameters.
Only simple UPDATE statements are supported. For example,
```
UPDATE t1 SET c3 = c3+? WHERE c1 = ? and c2 = 10;
```
Values changed in the C3 column can be constants and parameters, or a simple expression. C1 and C2 columns are indexed columns, followed by either constants or parameters.

Value range: Boolean

on indicates that the performance logs are output.
off indicates that the performance logs are not output.

Default value: on

advance_xlog_file_num

Parameter description: Specifies the number of Xlog files that are periodically initialized in advance in the background. This parameter is used to prevent the Xlog file initialization from affecting the performance during transaction submission. However, such a fault may occur only when the system is overloaded. Therefore, you do not need to set this parameter.

This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: an integer ranging from 0 to 100. The value 0 indicates that initialization is not performed in advance. For example, the value 10 indicates that the background thread periodically initializes 10 Xlog files in advance based on the write location of the current Xlog.

Default value: 0

enable_partition_opfusion

Parameter description: Specifies whether to optimize the query of the partition table during simple query when enable_opfusion is set to on.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the optimization feature is enabled.
off indicates that the optimization feature is disabled.

Default value: off

enable_beta_nestloop_fusion

Parameter description: Specifies whether to accelerate the execution of SQL statements, such as nestloop join, in TPC-C when enable_opfusion and enable_beta_opfusion are set to on.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

on indicates that the acceleration feature is enabled.
offindicates that the acceleration feature is disabled.

Default value: off

enable_beta_opfusion

Parameter description: Specifies whether to accelerate the execution of SQL statements, such as aggregate functions, sorting, and nestloop join, in TPC-C when enable_opfusion is set to on. For the nestloop join SQL statements, enable_beta_nestloop_fusion must be also set to on.

Value range: Boolean

Default value: off

sql_beta_feature

Parameter description: Specifies the SQL engine's optional beta features to be enabled, including optimization of row count estimation and query equivalence estimation.

These optional features provide optimization for specific scenarios, but performance deterioration may occur in some scenarios for which testing is not performed. In a specific customer scenario, you can set the query rewriting rules through this GUC parameter to achieve optimal query efficiency.

This parameter determines the combination of the SQL engine's beta features, for example, feature1, feature2, feature3, and feature4. You can perform the following settings:

-- Enable beta feature feature1 of the SQL engine.
set sql_beta_feature=feature1;
-- Enable beta features feature2 and feature3 of the SQL engine.
set sql_beta_feature=feature2,feature3;
-- Disable all optional beta features of the SQL engine.
set sql_beta_feature=none;

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string

none: None of the beta optimizer features is used.
sel_semi_poisson: Uses poisson distribution to calibrate the equivalent semi-join and anti-join selection rates.
sel_expr_instr: Uses the matching row count estimation method to provide more accurate estimation for instr(col, 'const') > 0, = 0, = 1.
param_path_gen: Generates more possible parameterized paths.
rand_cost_opt: Optimizes the random read cost of tables that have a small amount of data.
param_path_opt: Uses the bloat ratio of the table to optimize the analyze information of indexes.
page_est_opt: Optimizes the relpages estimation for the analyze information of non-column-store table indexes.

Default value: none

Issue