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
Copy file name to clipboardExpand all lines: README.md
+16Lines changed: 16 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -430,6 +430,22 @@ SELECT * FROM pathman_concurrent_part_tasks;
430
430
(1 row)
431
431
```
432
432
433
+
-`pathman_partition_list` in conjunction with `drop_range_partition()` can be used to drop RANGE partitions in a more flexible way compared to good old `DROP TABLE`:
434
+
```plpgsql
435
+
SELECT drop_range_partition(partition, false) /* move data to parent */
436
+
FROM pathman_partition_list
437
+
WHERE parent ='part_test'::regclass AND range_min::int<500;
438
+
NOTICE: 1 rows copied from part_test_11
439
+
NOTICE: 100 rows copied from part_test_1
440
+
NOTICE: 100 rows copied from part_test_2
441
+
drop_range_partition
442
+
----------------------
443
+
dummy_test_11
444
+
dummy_test_1
445
+
dummy_test_2
446
+
(3 rows)
447
+
```
448
+
433
449
### HASH partitioning
434
450
Consider an example of HASH partitioning. First create a table with some integer column:
0 commit comments