Partition management extension for PostgreSQL
part_config
table: maintenance_order
. If set, the partition sets will run in increasing numerical orderpart_config.maintenance_last_run
to track the last datetime that maintenance was run for that partition set. Timestamp is only updated if maintenance for that partition set completed successfully so can be used as a monitoring metric.infinite_time_partitions
flag to work even if the partition set has no data. This can happen in partition sets with retention and low data writes (Github Issue #585)partition_data
functions throwing an error if the source table was not in the same schema as the parent table. (Github Issue #639)pg_analyze
parameter to partition_gap_fill
function to allow skipping the analyze of a partition set if the gap fill actually creates new partitions. Note this is not an option in 5.x since the analyze step was refactored and never runs automatically during a call to the gap fill function anymore.part_config
and part_config_sub
tables before upgrading just to ensure they can be restored in case there are any issues. These tables are recreated as part of the upgrade.
part_config_pre_500_data
, part_config_sub_pre_500_data
type
in pg_partman will now refer to the types of delcarative partitioning that are supported. As of 5.0.1, only range
is supported, but others are in development (Github Issue #490).
part_config
and part_config_sub
tables have had some columns removed and rearranged to only contain supported features.information_schema.routine_privileges
& information_schema.table_privileges
YYYYMMDD
for intervals greater than or equal to 1 day and YYYYMMDD_HH24MISS
for intervals less than 1 day. Removed extra underscores to allow longer base partition names. Existing partition suffixes will still be supported, but newly created partition sets will use the new naming patterns by default. It is recommended that migration to the new suffixes is done when possible to ensure future support of possible pg_partman changes. The documentation on migrating the old specialized weekly/quarterly partition sets to be supported in 5.0.1 can be used as guidance for migrating other child table names as well.p_default_table
) (Github Issue #489).create_parent()
. Set p_template_table
to false
to skip template table creation. Note this is not a boolean since this parameter is also meant to take a template table name, so the explicit string value false
must be set (Github Issue #505).infinite_time_partitions
fixed. If set to true and data far ahead of "now" was inserted, no new child tables would be created based on the premake.show_partition_info()
clearer (Github Issue #542).For CHANGELOGs prior to version 5.0.0, see CHANGELOG-pre-5.0.0.txt
part_config
and part_config_sub
tables before upgrading just to ensure they can be restored in case there are any issues. These tables are recreated as part of the upgrade.
part_config_pre_500_data
, part_config_sub_pre_500_data
type
in pg_partman will now refer to the types of delcarative partitioning that are supported. As of 5.0.0, only range
is supported, but others are in development (Github Issue #490).
part_config
and part_config_sub
tables have had some columns removed and rearranged to only contain supported features.information_schema.routine_privileges
& information_schema.table_privileges
YYYYMMDD
for intervals greater than or equal to 1 day and YYYYMMDD_HH24MISS
for intervals less than 1 day. Removed extra underscores to allow longer base partition names. Existing partition suffixes will still be supported, but newly created partition sets will use the new naming patterns by default. It is recommended that migration to the new suffixes is done when possible to ensure future support of possible pg_partman changes. The documentation on migrating the old specialized weekly/quarterly partition sets to be supported in 5.0.0 can be used as guidance for migrating other child table names as well.p_default_table
) (Github Issue #489).create_parent()
. Set p_template_table
to false
to skip template table creation. Note this is not a boolean since this parameter is also meant to take a template table name, so the explicit string value false
must be set (Github Issue #505).infinite_time_partitions
fixed. If set to true and data far ahead of "now" was inserted, no new child tables would be created based on the premake.show_partition_info()
clearer (Github Issue #542).For CHANGELOGs prior to version 5.0.0, see CHANGELOG-pre-5.0.0.txt