Partition Management Function
proc_add_partition (relname regclass, boundaries_interval interval)
Description: Adds partitions to a table with the automatic partition creation function enabled.
Return type: void
Note: When the function is executed, multiple partitions with time range as boundaries_interval are created based on the existing partition boundary until new_part_boundary – now_time >= 29 * boundaries_interval. Then, an extra partition is created to ensure that at least a new partition is created when the function is executed.
Example:
1 2 3 4 5 |
call proc_add_partition('my_schema.my_table', interval '1 day'); proc_add_partition -------------------- (1 row) |
proc_drop_partition (relname regclass, older_than interval)
Description: Deletes partitions from a table with the automatic partition deletion function enabled.
Return type: void
Note: When this function is executed, all partitions in the table are traversed and the partitions whose boundary is smaller than now_time - older_than are deleted. If all partitions meet the deletion condition, the table is truncated with one partition kept.
Example:
1 2 3 4 5 |
call proc_drop_partition('my_schema.my_table', interval '7 day'); proc_drop_partition -------------------- (1 row) |
pg_partition_management_time(table_name, time)
Description: Modifies the execution time of the partition scheduling task that automatically adds or removes partitions. The default time is when the auto-increment partition table was created. This function is supported only by 8.3.0 and later versions.
Return value: SUCCESS, which indicates that the time is successfully modified.
Parameter:
- table_name indicates the name of the auto-increment partitioned table. The type is Name.
- time indicates the time when the data switching task is scheduled. The type is Time.
Example:
1 2 3 4 5 |
call pg_partition_management_time('partition_management_time','3:00'); pg_partition_management_time ------------------------------ SUCCESS (1 row) |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.