You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Performs RANGE partitioning for`relation` by partitioning key`attribute`.`start_value` argument specifies initial value,`interval` sets the rangeof values in a singlepartition,`count` is the number of premade partitions (if not set thenpathman tries to determine it based on attribute values). Partition creation callback is invoked for each partition if set beforehand.
106
+
Performs RANGE partitioning for`relation` by partitioning key`attribute`,`start_value` argument specifies initial value,`p_interval` sets thedefaultrangefor auto created partitions or partitions created with`append_range_partition()` or`prepend_range_partition()` (if`NULL` then autopartition creation feature won't work),`p_count` is the number of premade partitions (if not set then`pg_pathman` tries to determine it based on attribute values). Partition creation callback is invoked for each partition if set beforehand.
Merge two adjacent RANGE partitions. First, data from`partition2` is copied to`partition1`, then`partition2` is removed.
169
169
170
+
```plpgsql
171
+
merge_range_partitions(partitions REGCLASS[])
172
+
```
173
+
Merge several adjacent RANGE partitions (partitions must be specified in ascending or descending order). All the data will be accumulated in the first partition.
Create new RANGE partition for`relation` with specified range bounds.
196
+
Create new RANGE partition for`relation` with specified range bounds. If`start_value` or`end_value` are NULL then corresponding range bound will be infinite.