PostgreSQL Partition Manager (pg_partman) v4.3.0 has been released. This release contains important bug fixes for handling foreign keys and retention. Major new features include:
- A set of documentation for migrating an old trigger-based partition set to the native, declarative partitioning in PG11 or greater. Crunchy Data has also published this documentation as a blog post: https://info.crunchydata.com/blog/how-to-migrate-from-trigger-based-partitioning-to-native-in-postgresql - A table matrix in the documentation to more clearly outline which partition set properties are handled via inheritance from the parent table vs the template table feature of pg_partman. The template table is for assisting with partitioning features that are not yet handled fully with native partitioning: https://github.com/pgpartman/pg_partman/blob/master/doc/pg_partman.md#child-table-property-inheritance - A function for dumping out your pg_partman configuration for use when restoring a dump to another database. Thanks to James Coleman for this feature. - A function to backfill gaps in the child tables that may occur for various reasons during ongoing maintenance. Links Website - https://github.com/pgpartman/pg_partman Installation - https://github.com/pgpartman/pg_partman#installation Documentation - https://github.com/pgpartman/pg_partman/blob/master/doc/pg_partman.md Release Notes - https://github.com/pgpartman/pg_partman/blob/master/CHANGELOG.txt Crunchy Data - https://www.crunchydata.com Crunchy Data is proud to support the development and maintenance of pg_partman. -- Keith Fiske Senior Database Engineer Crunchy Data - http://crunchydata.com
