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
Allow changing the interval (daily,weekly,...) in an existing configuration
Previously it was not possible to switch to wider or shorter partitions after the initial setup.
The provisioning would recognize that the existing partitions do not match with the new interval specified in the configuration.
Now "interval" in be changed dynamically. Essentially the new code compares the existing partitions and the expected partitions by relying only the boundaries, ignoring the partition names.
Therefore it is also possible to use the partition manager on an existing set of partitions that do not follow its naming conventions.
For new partitions, if the range to create does not divide evenly by "interval", shorter partitions will
be created to fill the gaps. Their names are suffixed with dates formatted as YYYYMMDD_YYYYMMDD representing the partition bounds.
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -251,6 +251,9 @@ Partition object:
251
251
252
252
See the [full configuration file](configs/postgresql-partition-manager/postgresql-partition-manager.yaml).
253
253
254
+
## Work date
255
+
By default, the provisioning and cleanup evaluate what to do at the current date. For testing purposes, a different date can be set through the environment variable `PPM_WORK_DATE` (format: `YYYY-MM-DD`).
256
+
254
257
## Contributing
255
258
256
259
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
0 commit comments