[system] Settings

Specifies whether all blocks are to be rewritten by the COMBINE command. Setting this option to true can be used to avoid or undo block fragmentation introduced by partial update propagation.

Specifies whether all blocks are to be rewritten by the system-triggered propagation process. Setting this option to true can be used to avoid block fragmentation introduced by partial update propagation.

Specifies the maximum size for the main_wal_backups directory, which holds old main.wal files.

Note: The system will exceed the default value if it is necessary to keep a single old main.wal file that exceeds 2 GB.

Specifies the number of processing units in the system. This value is used to calculate the amount of memory available for each transaction.

For VectorH, num_cores is set based the number of cores on the master node only, but is set on each node. An equal number of cores on each node is assumed.

Num_cores is used to calculate the maximum parallelism level for a newly issued query if there are many queries already being executed. The goal is not to deteriorate the total throughput of the system. Generally, the higher the num_cores value, the higher parallelism levels are granted for queries running concurrently (where each parallelism level is not higher than max_parallelism_level).

Num_cores is used to derive a database-wide target on the number of concurrent threads used for parallel execution. Queries will run at a lower degree of parallelism if the default or requested degree would lead to an uneven allocation of resources to the new query based on the number of concurrently executing queries. On a system running many concurrent queries, new queries may get only one core and will more likely run out of memory since the num_cores value is used to reserve memory for possible other threads.

Default: Number of cores on the master node.

Tells Vector whether to attempt to merge concurrent updates on the same table. If set to false, the transaction that tries to commit last will fail and will have to abort. Disabling merging of concurrent updates can reduce memory consumption, especially if there are any long-running transactions in the system.

Uses SSE4.2 for accelerated string processing on CPU architectures that support it.

The Positional Delta Tree (PDT) is a data structure used for batch updates residing in memory. For more information, see Management of In-memory Updates.

Specifies an upper limit on total update memory consumption as a percentage of query memory limit (max_memory_size). When this limit is reached, the system propagates in-memory updates to disk.

Specifies the maximum number of retries for failed automatic update propagation. When propagation for a certain table fails, Vector will retry propagating this table if no alternative tables are possible.

Specifies a per-table maximum percentage of in-memory updates (that is, the number of updates divided by the number of stable tuples). When this limit is reached, the system propagates to disk in-memory updates for this table.

Specifies an upper limit on the total update memory in the snapshot layer of a transaction, as a percentage of query memory limit (max_memory_size). When this limit is reached, the system will not allow further update operations in this transaction.

Specifies the minimum number of tuples in a table above which max_table_update_ratio is checked. This is to avoid frequent update propagation to disk on relatively small tables.

Enables or disables system-triggered propagation of in-memory updates. Valid values are true and false.

Note: Disabling automatic propagation overrides the max_global_update_memory setting and can lead to unwanted consequences if query memory becomes full with PDTs.