Overview
default_progressive_merge_num specifies the default number of progressive merges for a newly created table.
Privilege requirements
Query parameters
Both the
systenant and all user tenants can query this parameter using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify parameters
Both the
systenant and user tenants can modify this parameter.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | Int |
| Default Value | 0 |
| Value range | [0, +∞) |
| Modifiable | Yes, you can use the following methods:ALTER SYSTEM SETStatement modification. |
| Whether to restart the OBServer node for the change to take effect | No, the setting takes effect immediately. |
Usage instructions
OceanBase AI Database supports progressive major compaction for table data. After performing a DDL operation that requires data rewriting on a table, the data rewriting can be distributed across multiple major compactions, with only a portion of the data being rewritten in each compaction. You can control the major compaction behavior using the table-level attribute progressive_merge_num, or set the default number of progressive major compactions for a new table using the configuration parameter default_progressive_merge_num.
If you do not specify the progressive_merge_num attribute for a new table, the system sets the table-level progressive_merge_num value to the value of default_progressive_merge_num.
The values of the progressive_merge_num attribute are as follows:
- When progressive_merge_num = 0, the default value of 100 is used.
- progressive_merge_num = 1 indicates that a full compaction is always performed, and incremental or progressive compactions are not performed.
- When progressive_merge_num = X, it indicates that all data is rewritten in X major compactions, with each round rewriting 1/X of the data.
Configuration example
Set the default number of progressive major compactions for a new table to the default value of 100.
obclient> ALTER SYSTEM SET default_progressive_merge_num = 0;