PostgreSQL Partition Manager (pg_partman) v4.6.0 has been released.

IMPORTANT REQUEST: A topic has been opened on the github page to discuss the future development of pg_partman and support for trigger-based partitioning. A plan is currently in place to begin dropping trigger-based support upon the EOL for PostgreSQL 10 on November 10, 2022. Feedback is requested for use-cases that could potentially change these plans and continue supporting trigger-based partitioning until native partitioning better supports them.

https://github.com/pgpartman/pg_partman/discussions/360

Version 4.6.0 brings significantly better support for partitioning with arbitrary time interval values. Other changes of note are:

• PostgreSQL 14 support
• Deprecation of pg_partman's specialized UPSERT support for PG 11 and greater. Usage of the built-in INSERT ... ON CONFLICT feature is better supported in native partitioning as of version 11.
• When dropping child tables for retention, DROP ... CASCADE is no longer supported in native partitioning. This avoids the foreign key references to the partition set being dropped completely whenever a child table is dropped.
• Additional features and bug fixes for this release can be found in the CHANGELOG.

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