Settings

wal_level

Parameter description: Specifies the level of information to be written to the WAL. The value cannot be empty or commented out.

• To enable WAL archiving and data streaming replication between the primary and standby nodes, set this parameter to archive, hot_standby, or logical.
• If this parameter is set to minimal, hot_standby must be set to off, and max_wal_senders must be set to 0. In addition, the database must be deployed in a standalone system. Otherwise, the database cannot be started.
• If this parameter is set to archive, hot_standby must be set to off. Otherwise, the database startup fails. However, hot_standby cannot be set to off in an HA cluster. For details, see the description of the hot_standby parameter.

Value type: enumerated type

Value range:

• minimal

  Advantages: Certain bulk operations (including creating tables and indexes, executing cluster operations, and copying tables) are safely skipped in logging, which can make those operations much faster.

  Disadvantages: WALs contain only basic information required for recovery from a database server crash or an emergency shutdown. Data cannot be restored from archived WALs.

• archive

  Adds logging required for WAL archiving, supporting the database restoration from archives.

• hot_standby
  • Further adds information required to run SQL queries on a standby node and takes effect after the database restarts.
  • To enable read-only queries on a standby node, the wal_level parameter must be set to hot_standby on the primary node and the same value must be set on the standby node. There are few measurable differences in performance between using hot_standby and archive levels. However, feedback is welcome if any differences in their impacts on product performance are noticeable.
• logical

  This parameter indicates that WALs support logical replication.

Default value: hot_standby

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

Setting suggestion: Set this parameter to logical when the logical replication function is enabled. In other scenarios, set this parameter to hot_standby.

fsync

Parameter description: Specifies whether the GaussDB server uses the fsync() function (see wal_sync_method) to ensure that updates can be written to disks in a timely manner.

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

• Using the fsync() function ensures that the data can be recovered to a known state when the OS or hardware crashes.
• Setting this parameter to off may result in unrecoverable data corruption in a system crash.

Value range: Boolean

• on indicates that the fsync() function is used.
• off indicates that the fsync() function is not used.

Default value: on

synchronous_commit

Parameter description: Specifies the synchronization mode of the current transaction.

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

Value range: enumerated values

• 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

This parameter is maintained by the CM. If it is manually modified, data may be lost. For details, see "Unified Cluster Management Tool > Features > Automatic Copy Addition and Reduction by Shard > Remarks" in Tool Reference.

wal_sync_method

Parameter description: Specifies the method used for forcing WAL updates out to disk.

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

If fsync is set to off, the setting of this parameter does not take effect because WAL updates will not be forcibly written to disks.

Value range: enumerated values

• open_datasync indicates that WAL files are opened with the O_DSYNC option.
• fdatasync indicates that fdatasync() is called at each commit (SUSE 10 and SUSE 11 are supported).
• fsync_writethrough indicates that fsync() is called at each commit to force data in the buffer to be written to disks.
  

  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 on the Windows platform.

• fsync indicates that fsync() is called at each commit. (SUSE 10 and SUSE 11 are supported.)
• open_sync indicates that open() with the O_SYNC option is used to write WAL files (SUSE 10 and SUSE 11 are supported).
  

  Not all platforms support the preceding parameters.

Default value: fdatasync

full_page_writes

Parameter description: Specifies whether the GaussDB server writes the entire content of each disk page to WALs during the first modification of that page after a checkpoint. When both enable_incremental_checkpoint and enable_double_write are enabled, full_page_writes is not used.

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

• This parameter is needed because a page write that is in process during an OS crash might be only partially completed, leading to an on-disk page that contains a mix of old and new data. The row-level change data normally stored in WALs will not be enough to completely restore such a page during post-crash recovery. Storing the full page image guarantees that the page can be correctly restored, but at the price of increasing the amount of data that must be written to WALs.
• Setting this parameter to off might lead to unrecoverable data corruption after a system failure. It might be safe to set this parameter to off if you have hardware (such as a battery-backed disk controller) or file-system software (such as ReiserFS 4) that reduces the risk of partial page writes to an acceptably low level.

Value range: Boolean

• on indicates that this feature is enabled.
• off indicates that this feature is disabled.

Default value: on

wal_log_hints

Parameter description: Specifies whether to write an entire page to WALs during the first modification of that page after a checkpoint, even for non-critical modifications of so-called hint bits. You are advised not to modify the setting.

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

Value range: Boolean

• on indicates that the entire page is written to WALs.
• off indicates that the entire page is not written to WALs.

Default value: on

wal_buffers

Parameter description: Specifies the size of shared memory for storing WALs, in multiples of XLOG_BLCKSZ or the actual size. XLOG_BLCKSZ indicates the size of an Xlog block, typically 8 KB.

Parameter type: integer.

Unit: 8 kB (XLOG_BLCKSZ size)

Value range: –1, or 4 to 2¹⁸. The minimum value is –1 and the maximum value is 262144 (number of XLOG_BLCKSZ).

• If this parameter is set to –1, the value of wal_buffers is automatically adjusted based on the value of shared_buffers. The default value of wal_buffers is 1/32 of shared_buffers. The minimum value is XLOG_BLCKSZ multiplied by 8 and the maximum value is XLOG_BLCKSZ multiplied by 2048. If the automatically adjusted value is less than the minimum value, the value is forcibly set to the minimum value. If the value is greater than the maximum value, the value is forcibly set to the maximum value.
• If this parameter is set to a value smaller than 4 (that is, 0, 1, 2, or 3), the value 4 is forcibly used.

Default value:

1GB (196-core CPU/1536 GB memory, 128-core CPU/1024 GB memory, 104-core CPU/1024 GB memory, 96-core CPU/1024 GB memory, 96-core CPU/768 GB memory, 80-core CPU/640 GB memory, 64-core CPU/512 GB memory, 60-core CPU/480 GB memory, 32-core CPU/256 GB memory); 512MB (16-core CPU/128 GB memory); 256MB (8-core CPU/64 GB memory); 128MB (4-core CPU/32 GB memory); 16MB (4-core CPU/16 GB memory)

Setting method: This is a POSTMASTER parameter. Set it based on instructions provided in Table 1. For example, the value 2048 indicates that wal_buffers is 2048 x 8 KB, and the value 20480kB indicates that wal_buffers is 20480KB. If the value contains a unit, the value must be KB, MB, or GB and must be an integer multiple of 8 KB.

Setting suggestion: The content of the WAL buffer is written to disks at every transaction commit. Therefore, setting an extremely large value is unlikely to bring a significant increase in system performance. However, setting this parameter to a few megabytes can improve the disk write performance on a server where a large number of transactions are committed at the same time. The default value meets user requirements in most cases. You are advised to retain it. Do not set wal_buffers to an excessively large or small value, and the following condition must be true: data_replicate_buffer_size + segment_buffers + shared_buffers + wal_buffers + temp_buffers + maintenance_work_mem + work_mem + query_mem + (Standby node) wal_receiver_buffer_size < max_process_memory < Memory size of the physical machine. If the value of the memory parameter is too large and exceeds the upper limit of the physical memory, the database fails to be started because no sufficient memory can be allocated.

wal_writer_delay

Parameter description: Specifies the delay between activity rounds for the WAL writer.

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

A longer delay might lead to insufficient WAL buffer and a shorter delay leads to continuously writing of the WALs, thereby increasing the load of disk I/O.

Value range: an integer ranging from 1 to 10000. The unit is millisecond.

Default value: 200ms

commit_delay

Parameter description: Specifies the duration for committed data to be stored in the WAL buffer.

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

• When this parameter is set to a non-zero value, the committed transaction is stored in the WAL buffer instead of being written to the WAL immediately. Then the WAL writer flushes the buffer to disks periodically.
• If system load is high, other transactions are probably ready to be committed within the delay. If no other transactions are ready to be committed, the delay is a waste of time.

Value range: an integer ranging from 0 to 100000. The unit is μs. 0 indicates no delay.

Default value: 0

commit_siblings

Parameter description: Specifies a threshold on the number of concurrent transactions when a transaction initiates a commit request. If the number of concurrent transactions is greater than the value of this parameter, the transaction will wait for a period of time specified by commit_delay. Otherwise, this transaction is written into WALs immediately.

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

Value range: an integer ranging from 0 to 1000

Default value: 5

wal_block_size

Parameter description: Specifies the size of a WAL disk block.

This is a fixed INTERNAL parameter. It can be viewed but cannot be modified.

Value range: an integer. The unit is byte.

Default value: 8192

wal_segment_size

Parameter description: Specifies the size of a WAL segment file.

This is a fixed INTERNAL parameter. It can be viewed but cannot be modified.

Value range: an integer. The unit is 8 KB.

Default value: 16MB (2048 x 8 KB)

walwriter_cpu_bind

Parameter description: Binds the WAL writer thread to a specified CPU core.

Parameter type: integer.

Unit: none

Value range: –1 to the number of cores minus 1. CPU cores are numbered starting from 0.

• –1: indicates that CPU core binding is not performed.
• N: indicates that the WAL writer thread is bound to CPU core N.

Default value: –1

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

Setting suggestion: Retain the default value.

wal_sender_bind_cpu_attr

Parameter description: Specifies the core binding operation of the log sender thread. Only the sysadmin user can access this parameter.

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

• 'nobind': The thread is not bound to a core.
• 'cpuorderbind: 8-12': One thread is bound to one core starting from core 8. If the number of cores in the range is insufficient, the remaining threads are not bound. You are advised to set the interval to a value greater than or equal to the value of max_wal_senders.

Value range: a string of more than 0 characters. The value is case-insensitive.

Default value: 'nobind'

walwriteraux_bind_cpu

Parameter description: Specifies the CPU core bound to the auxiliary log writer thread.

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

Value range: an integer ranging from –1 to the number of cores minus 1.

Default value: –1

walwriter_sleep_threshold

Parameter description: Specifies the number of times that idle Xlogs are refreshed before the Xlog flusher enters the sleep state. If the number of times reaches the threshold, the Xlog flusher enters the sleep state.

Parameter type: integer.

Unit: none

Value range: 1 to 50000

Default value: 500 (196-core CPU/1536 GB memory, 128-core CPU/1024 GB memory, 104-core CPU/1024 GB memory, 96-core CPU/1024 GB memory, 96-core CPU/768 GB memory, 80-core CPU/640 GB memory, 64-core CPU/512 GB memory, and 60-core CPU/480 GB memory); 50 (32-core CPU/256 GB memory, 16-core CPU/128 GB memory, 8-core CPU/64 GB memory, 4-core CPU/32 GB memory, and 4-core CPU/16 GB memory)

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

Setting suggestion: Retain the default value.

wal_file_init_num

Parameter description: Specifies the number of Xlog segment files created at a time when the WAL writer thread is started.

Parameter type: integer.

Unit: none

Value range: 0 to 1000000

Default value: 10 (196-core CPU/1536 GB memory, 128-core CPU/1024 GB memory, 104-core CPU/1024 GB memory, 96-core CPU/1024 GB memory, 96-core CPU/768 GB memory, 80-core CPU/640 GB memory, 64-core CPU/512 GB memory, and 60-core CPU/480 GB memory); 0 (32-core CPU/256 GB memory, 16-core CPU/128 GB memory, 8-core CPU/64 GB memory, 4-core CPU/32 GB memory, and 4-core CPU/16 GB memory)

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

Setting suggestion: Retain the default value.

wal_file_preinit_bounds

Parameter description: Specifies the maximum number of WAL segment files that can be pre-expanded by the WAL writer auxiliary thread per second during service running. The WAL segment file size is 16 MB. If this parameter is set to 0, there is no restriction.

Parameter type: integer

Unit: none

Value range: [0,1024]

Default value: 0

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

Setting suggestion: Retain the default value. Set this parameter to a valid value based on the disk I/O capability. For details, see the value of max_io_capacity.

• If max_io_capacity is set to 500MB, set this parameter to 25.
• If max_io_capacity is set to 1GB, set this parameter to 50.

xlog_file_path

Parameter description: Specifies the path of the Xlog shared disk in dual-database instance shared storage scenarios. This parameter is configured by the OM during database system initialization. You are advised not to modify the configuration.

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

Value range: a string.

Default value: NULL

xlog_file_size

Parameter description: Specifies the size of the Xlog shared disk in dual-database instance shared storage scenarios. This parameter is configured by the OM during database system initialization. You are advised not to modify the configuration.

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

Value range: a long integer ranging from 5053733504 to 576460752303423487. The unit is byte.

Default value: 549755813888

xlog_lock_file_path

Parameter description: Specifies the path of the lock file preempted by the Xlog shared disk in dual-database instance shared storage scenarios. This parameter is configured by the OM during database system initialization. You are advised not to modify the configuration.

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

Value range: a string.

Default value: NULL

max_size_for_shared_storage_xlog_write

Parameter description: Specifies the maximum amount of data that can be written to a shared disk at a time.

Parameter type: integer.

Unit: KB

Value range: 8–131072

Default value: 1024

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

Setting suggestion: none

force_promote

Parameter description: Specifies whether to enable the forcible switchover function on the standby node.

When a database instance is faulty, the forcible switchover enables the database instance to recover services as soon as possible at the cost of losing some data. This is an escape method used when the database instance is unavailable. You are advised not to trigger this method frequently. You are advised not to use this function if you are not clear about the impact of data loss on services.

To use this function, you need to enable it on the DN and CM Server and restart the database instance for the setting to take effect. For details about how to enable the forcible switchover function on the standby node, see "Emergency Handling > Performing a Forcible Primary/Standby Switchover" in Troubleshooting.

Value range: 0 or 1

The value 0 indicates that the function is disabled, and the value 1 indicates that the function is enabled.

Default value: 0

wal_debug

Parameter description: Specifies whether to output WAL-related debugging information. This parameter is available only when WAL_DEBUG is enabled during compilation.

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

Value range: Boolean

Default value: false

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 is a SIGHUP parameter. Set it based on instructions provided in Table 1.

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:

2us (196-core CPU/1536 GB memory, 128-core CPU/1024 GB memory, 104-core CPU/1024 GB memory, 96-core CPU/1024 GB memory, 96-core CPU/768 GB memory, 80-core CPU/640 GB memory, 64-core CPU/512 GB memory, 60-core CPU/480 GB memory, 32-core CPU/256 GB memory, 16-core CPU/128 GB memory, 8-core CPU/64 GB memory, 4-core CPU/32 GB memory); 800us (4-core CPU/16 GB memory)

wal_flush_delay

Parameter description: Specifies the wait interval when an entry in the WAL_NOT_COPIED state is encountered during WalInsertStatusEntryTbl traversal.

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

Value range: an integer ranging from 0 to 90000000 (μs)

Default value:

1us (196-core CPU/1536 GB memory, 128-core CPU/1024 GB memory, 104-core CPU/1024 GB memory, 96-core CPU/1024 GB memory, 96-core CPU/768 GB memory, 80-core CPU/640 GB memory, 64-core CPU/512 GB memory, 60-core CPU/480 GB memory, 32-core CPU/256 GB memory, 16-core CPU/128 GB memory, 8-core CPU/64 GB memory, 4-core CPU/32 GB memory); 100us (4-core CPU/16 GB memory)

wal_receiver_bind_cpu

Parameter description: Specifies the CPU core ID bound to the WAL receiver thread.

The default value is –1, which is an invalid value, indicating that cores are not bound.

Although the value range is INT_MAX, the actual value is related to the number of used device cores. If the specified CPU core ID does not exist, an error is reported and core binding is interrupted.

Multiple threads can be bound to one core, but the performance deteriorates. Therefore, you are advised not to bind multiple threads to one core.

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

Value range: a value ranging from –1 to INT_MAX.

Default value: –1

wal_rec_writer_bind_cpu

Parameter description: Specifies the CPU core ID bound to the WAL rec writer thread.

The default value is –1, which is an invalid value, indicating that cores are not bound.

Although the value range is INT_MAX, the actual value is related to the number of used device cores. If the specified CPU core ID does not exist, an error is reported and core binding is interrupted.

Multiple threads can be bound to one core, but the performance deteriorates. Therefore, you are advised not to bind multiple threads to one core.

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

Value range: a value ranging from –1 to INT_MAX.

Default value: –1