-
Hello, But since then, there are no new weekly partitions been created (should have been at least 2 more base on ISO week convention). My questions are
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
By default, no new partitions are created by pg_partman unless new data has been added to the partition set. All future partition creation is managed by calling the run_maintenance() function on a regular basis. New child tables are not automatically created simply based on incoming data to avoid contention issues. You can either call run maintenance via cron or you can use the built in background worker (see documentation). If you had added new data, and there are appropriate child tables for that data, it should go to those child tables. If there is no matching child table for that data, then it goes to the default. You will then have to use the partition_data_*() functions/procedures to move that data out to the proper child tables. |
Beta Was this translation helpful? Give feedback.
-
@keithf4, What is the preferred way to execute |
Beta Was this translation helpful? Give feedback.
-
Never mind, that was a dumb question :-). I'll run it in a lambda. |
Beta Was this translation helpful? Give feedback.
By default, no new partitions are created by pg_partman unless new data has been added to the partition set. All future partition creation is managed by calling the run_maintenance() function on a regular basis. New child tables are not automatically created simply based on incoming data to avoid contention issues. You can either call run maintenance via cron or you can use the built in background worker (see documentation).
If you had added new data, and there are appropriate child tables for that data, it should go to those child tables. If there is no matching child table for that data, then it goes to the default. You will then have to use the partition_data_*() functions/procedures t…