Miscellaneous Parameters

enable_default_ustore_table

Parameter description: Specifies whether to enable the Ustore storage engine by default. If this parameter is set to on, all created tables are Ustore tables.

This is a USERSET parameter. Set it based on instructions provided in Table 1. Note that the track_counts and track_activities parameters must be enabled when the Ustore table is used. Otherwise, space expansion may occur.

Value range: [off,on]

Default value: on

enable_ustore

Parameter description: Specifies whether to enable the Ustore storage engine. If this parameter is set to on, Ustore tables can be created. Note that the track_counts and track_activities parameters must be enabled when the Ustore table is used. Otherwise, space expansion may occur.

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

Value range: [off,on]

Default value: on

reserve_space_for_nullable_atts

Parameter description: Specifies whether to reserve space for the nullable attribute of an Ustore table. If this parameter is set to on, space is reserved for the nullable attribute of the Ustore table by default.

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

Value range: [off,on]

Default value: on

server_version

Parameter description: Specifies the server version number.

This is a fixed parameter of the INTERNAL type. It can be viewed but cannot be modified. This parameter is inherited from the PostgreSQL kernel, indicating that the current database kernel is compatible with the server_version version corresponding to PostgreSQL. This parameter is reserved to ensure the ecosystem compatibility of the northbound external tool API (query when the tool is connected). This parameter is not recommended. To query the server version, use the opengauss_version() function.

Value range: a string

Default value: 9.2.4

server_version_num

Parameter description: Specifies the server version number.

This is a fixed parameter of the INTERNAL type. It can be viewed but cannot be modified. This parameter is inherited from the PostgreSQL kernel, indicating that the current database kernel is compatible with the server_version_num version corresponding to PostgreSQL. This parameter is reserved to ensure the ecosystem compatibility of the northbound external tool API (query when the tool is connected).

Value range: an integer

Default value: 90204

block_size

Parameter description: Specifies the block size of the current database.

This is a fixed INTERNAL parameter and cannot be modified.

Value: 8192

Default value: 8192

segment_size

Parameter description: Specifies the segment file size of the current database.

This is a fixed INTERNAL parameter and cannot be modified.

Unit: 8 KB

Default value: 131072, that is, 1 GB

max_index_keys

Parameter description: Specifies the maximum number of index keys supported by the current database.

This is a fixed INTERNAL parameter and cannot be modified.

Default value: 32

integer_datetimes

Parameter description: Specifies whether the date and time are in the 64-bit integer format.

This is a fixed INTERNAL parameter and cannot be modified.

Value range: Boolean

• on: yes.
• off: no.

Default value: on

lc_collate

Parameter description: Specifies the locale in which sorting of textual data is done.

This is a fixed INTERNAL parameter and cannot be modified.

Default value: Determined by the configuration set during the database installation and deployment.

lc_ctype

Parameter description: Specifies the locale that determines character classifications. For example, it specifies what a letter and its upper-case equivalent are.

This is a fixed INTERNAL parameter and cannot be modified.

Default value: Determined by the configuration set during the database installation and deployment.

max_identifier_length

Parameter description: Specifies the maximum identifier length.

This is a fixed INTERNAL parameter and cannot be modified.

Value range: an integer

Default value: 63

server_encoding

Parameter description: Specifies the database encoding (character set).

By default, gs_initdb will initialize the setting of this parameter based on the current system environment. You can also run the locale command to check the current configuration environment.

This is a fixed INTERNAL parameter and cannot be modified.

Default value: determined by the current system environment when the database is created.

enable_upgrade_merge_lock_mode

Parameter description: If this parameter is set to on, the delta merge operation internally increases the lock level, and errors can be prevented when update and delete operations are performed at the same time.

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

Value range: Boolean

• If this parameter is set to on, the delta merge operation internally increases the lock level. In this way, when the DELTAMERGE operation is concurrently performed with the UPDATE or DELETE operation, one operation can be performed only after the previous one is complete.
• If this parameter is set to off and the DELTAMERGE operation is concurrently performed with the UPDATE or DELETE operation to the data in a row in the delta table of the table, errors will be reported during the later operation, and the operation will stop.

Default value: off

transparent_encrypted_string

Parameter description: This parameter is discarded. It stores a sample string that is transparently encrypted. After the fixed string TRANS_ENCRYPT_SAMPLE_STRING is encrypted using a database encryption key, ciphertext is obtained to check whether the DEK obtained during second startup is correct. If it is incorrect, database nodes will not be started. This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1.

Value range: a string. An empty string indicates that the entire database is a not encrypted.

Default value: empty

Do not set this parameter manually. Otherwise, the database may become faulty.

transparent_encrypt_kms_url

Parameter description: This parameter is discarded. It stores the address for obtaining the database key that is transparently encrypted. The content must contain only the characters specified in RFC3986, and the maximum length is 2047 bytes. The format is kms://Protocol@KMS host name 1;KMS host name 2:KMS port number/kms, for example, kms://https@linux175:29800/.

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

Value range: a string

Default value: empty

transparent_encrypt_kms_region

Parameter description: This parameter is discarded. It stores the deployment region of the entire database. The content must contain only the characters specified in RFC3986, and the maximum length is 2047 bytes.

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

Value range: a string

Default value: empty

basebackup_timeout

Parameter description: Specifies the timeout interval for a connection that has no read or write operations after a backup transfer is complete.

When the gs_basebackup tool is used for transmission and a high compression rate is specified, the transmission of the tablespace may time out (the client needs to compress the transmitted data).

Value range: an integer ranging from 0 to INT_MAX. The unit is s. 0 indicates that archiving timeout is disabled.

Default value: 600s

datanode_heartbeat_interval

Parameter description: Specifies the interval at which heartbeat messages are sent between heartbeat threads. You are advised to set this parameter to a value no more than wal_receiver_timeout/2.

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

Value range: an integer ranging from 1000 to 60000. The unit is ms.

Default value: 1s

max_concurrent_autonomous_transactions

Parameter description: Specifies the maximum number of autonomous transaction connections, that is, the maximum number of concurrent autonomous transactions executed at the same time. If this parameter is set to 0, autonomous transactions cannot be executed.

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

Value range: 0–10000. The theoretical maximum value is 10000, and the actual maximum value is a dynamic value. The calculation formula is 262143 – job_queue_processes – autovacuum_max_workers – max_inner_tool_connections – max_connections – AUXILIARY_BACKENDS – AV_LAUNCHER_PROCS. The values of job_queue_processes, autovacuum_max_workers, max_inner_tool_connections, and max_connections depend on the settings of the corresponding GUC parameters. AUXILIARY_BACKENDS indicates the number of reserved auxiliary threads and is fixed to 20. AV_LAUNCHER_PROCS indicates the number of reserved launcher threads for autovacuum, which is fixed to 2.

Default value:

200 (196-core CPU/1536 GB memory, 128-core CPU/1024 GB memory, 104-core CPU/1024 GB memory, 96-core CPU/1024 GB memory); 150 (96-core CPU/768 GB memory); 120 (80-core CPU/640 GB memory) 100 (64-core CPU/512 GB memory); 80 (60-core CPU/480 GB memory); 40 (32-core CPU/256 GB memory); 20 (16-core CPU/128 GB memory); 10 (8-core CPU/64 GB memory, 4-core CPU/32 GB memory, 4-core CPU/16 GB memory)

Suggestion: Set this parameter based on actual service requirements and hardware configurations. It is recommended that this parameter be set to a value less than or equal to 1/10 of max_connections. If you only increase the value of this parameter but do not adjust the memory parameters in the same proportion, the memory may be insufficient and the error message "memory is temporarily unavailable" is displayed when the service load is heavy.

If the value range of this parameter is changed during the upgrade and the value is changed before the commit operation, you need to change the value range to the value allowed before the upgrade if you roll back the upgrade. Otherwise, the database may fail to be started.

enable_seqscan_fusion

Parameter description: Specifies whether to enable SeqScan optimization.

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

Value range: Boolean

• on indicates that SeqScan optimization is enabled.
• off indicates that SeqScan optimization is disabled.

Default value: off

This parameter can be used to optimize only the execution time of the seqscan operator in the EXPLAIN ANALYZE statement.

cluster_run_mode

Parameter description: Specifies whether a DN belongs to the primary or standby database instance in the dual-database instance DR scenario. For a single database instance, use the default primary database instance.

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

Value range: enumerated values

• cluster_primary indicates the primary database instance.
• cluster_standby indicates the standby database instance.

Default value: cluster_primary

acceleration_with_compute_pool

Parameter description: Determines whether to use the computing resource pool for acceleration when an OBS is queried. (Due to specification changes, the current version no longer supports this feature. Do not use it.)

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

Value range: Boolean

• on indicates that the query covering the OBS is accelerated based on the cost when the computing resource pool is available.
• off indicates that no query is accelerated using the computing resource pool.

Default value: off

dfs_partition_directory_length

Parameter description: Specifies the maximum directory name length for the partition directory of a table partitioned by VALUE in the HDFS.

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

Value range: 92 to 7999

Default value: 512

max_resource_package

Parameter description: Specifies the maximum number of threads that each DN can run concurrently on an acceleration database instance on the cloud.

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

Value range: 0 to 2147483647

Default value: 0

enable_gpi_auto_update

Parameter description: Determines whether global indexes are updated by default in partition DDL commands.

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

Value range: Boolean

• The value on indicates that global indexes are updated regardless of whether the partition DDL commands contain the UPDATE GLOBAL INDEX clause.
• The value off indicates that global indexes are not updated unless the partition DDL commands contain the UPDATE GLOBAL INDEX clause.

Default value: off